Johto Data

Johto Data Document Search

document_search

Read-only

Rank up to 200 caller-supplied documents with lexical BM25 and return top matches, scores and exact snippet offsets. No web search, embeddings or external fetches. Caller must have rights to supplied text. Costs $0.0018 USDC per call via x402. Without payment, the call returns the x402 payment requirements; retry with an X-PAYMENT or PAYMENT-SIGNATURE header, or params._meta["x402/payment"].

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>",
      "documents": "<documents>"
    },
    "name": "document_search"
  }
}

Input Schema

Name	Required	Description
`topK`	No
`query`	Yes	Query, max 2000 characters
`documents`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations cover only readOnly/openWorld; the description adds the traits that actually matter: per-call cost ($0.0018 USDC via x402), the unpaid-call behavior (returns payment requirements), and the exact retry mechanisms (X-PAYMENT / PAYMENT-SIGNATURE header or params._meta payment). It also discloses the return shape (matches, scores, snippet offsets).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences, front-loaded with what the tool does, then scope exclusions, then the payment mechanics. No filler or repetition of the name/title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description still specifies the return contents and snippet offsets, plus the full payment negotiation loop. For a read-only, closed-world ranking tool with a paid gateway, the agent has everything needed to invoke it correctly on first try.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, so the description should compensate more. It restates the 200-document cap and implies topK through 'top matches,' but says nothing about the topK range/default or how query and document text constraints interact; the query text limit is only in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (rank), resource (caller-supplied documents), method (lexical BM25), and scope (up to 200). It explicitly excludes web search, embeddings, and external fetches, so an agent can tell precisely what this tool does and does not do.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The negatives ('No web search, embeddings or external fetches') effectively tell an agent when NOT to reach for this tool and point toward alternative approaches. There is no comparison to a named sibling, but none in the sibling list is a document search, so this is close to complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Johto Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?