Tool Argument Completeness Checker Connector for AI agents.

You can use the Capability Argument Completeness Checker to validate arguments before they are executed. This prevents broken calls from ever reaching your backend.

Yes. By comparing extracted text against your provided list of valid enums, the Capability Argument Completeness Checker flags any hallucinated values immediately.

Yes, it works with any MCP-compatible client like Claude, Cursor, or Windsurf. It acts as a validation layer for whatever agent you are using.

Absolutely. It identifies exactly which required parameters were left out of the proposed action text so you can fix them before execution.

It is essential for complex workflows where accuracy is critical. It ensures that every capability call contains the necessary data to succeed without errors.

The check_argument_completeness capability compares any extracted argument values against a provided JSON object of valid enums. If an extracted value is not present in the allowed set, it is flagged as a hallucination.

You must provide requiredArgsJson as a JSON array of strings and validEnumsJson as a JSON object mapping argument names to arrays of allowed values.

Yes, the capability uses regex and keyword indexing to parse unstructured text, making it capable of extracting values from natural language descriptions of capability calls.

It compares the extracted argument values against a provided list of valid enums using tool_validate_extraction. If a value is found that isn't in the list, it is flagged as a hallucination.

A missing argument is a required field that was not mentioned in the text at all. A hallucination is a field that was mentioned, but with an invalid value that does not match the allowed set.

Yes, you can use tool_extract_raw_matches to perform a low-level scan of text using specific keywords as anchors to find potential argument-value pairs.