Detect ambiguous tool schemas API

Flag generic tool names, generic parameter names, and descriptions that repeat the name or are missing. Matching is against a fixed word list, not a language model.

The Detect ambiguous tool schemas operation is part of the Agent Tool Schema Intelligence API on BRAINIAC.software. Flag generic tool names, generic parameter names, and descriptions that repeat the name or are missing. Matching is against a fixed word list, not a language model. It is exposed as POST /api/v1/agent-tool-schema/tool-schema-ambiguity-detect and priced at $0.03 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied tool definitions, JSON Schema objects, and OpenAPI documents processed locally Limitations: No schema URL is fetched and no language model reads the text. Keyword checks cover JSON Schema draft-07, JSON Schema 2020-12, OpenAPI 3.0, and OpenAPI 3.1. Two tools are not treated as duplicates only because they share a few words. Token figures are characters divided by four, not a provider tokenizer. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Lint agent tool schemas, Detect overlapping tool schemas, Validate tool request examples, Audit tool required fields. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.03 USDC
/api/v1/agent-tool-schema/tool-schema-ambiguity-detect

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/agent-tool-schema/tool-schema-ambiguity-detect" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "tools": [
    {
      "name": "run",
      "description": "run",
      "parameters": {
        "type": "object",
        "properties": {
          "data": {
            "type": "string"
          }
        }
      }
    },
    {
      "name": "SearchOrders",
      "description": "Search stored orders by the customer email address."
    },
    {
      "name": "search_orders",
      "description": "Search stored orders by the customer email address and return the matching rows."
    }
  ]
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Agent Tool Schema Intelligence APIFull docsHow it works