Skip to main content
Glama

AutoPay

search

Queue a cited web lookup ($0.01). Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key. Returns 202 with job_id. Typical ETA 10–20 minutes; poll get_job.

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>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses the $0.01 cost, the two payment/auth paths (X-PAYMENT x402 USDC on Base or a prepaid API key), that the call is asynchronous and returns 202 with a job_id, and realistic latency. It stops short of covering failure behavior, whether a failed job is still charged, or rate limits, so it is not exhaustive.

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?

Three dense sentences with zero filler: purpose first, then payment mechanics, then the return value and next step. Every clause carries operational information an agent needs before calling.

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

Completeness4/5

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

For a tool with no annotations and no output schema, the description covers the critical unknowns: cost, auth, async return shape, latency, and the follow-up call. It is missing failure/refund semantics and how results are retrieved beyond polling, but an agent can invoke it correctly from what is written.

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

Parameters2/5

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

The single parameter has 0% schema description coverage, so the description must explain what `query` accepts, but it says nothing about whether it takes a natural-language question, keywords, or constraints like length or citation preferences. Only the parameter's name in the schema conveys its meaning.

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

Purpose4/5

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

"Queue a cited web lookup" gives a specific verb (queue) and resource (cited web lookup), making the asynchronous nature unmistakable. It explicitly distinguishes itself from the polling sibling get_job, though it does not differentiate from fetch, research, or verify, so a 4 rather than a 5.

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

Usage Guidelines3/5

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

The definition supplies workflow context (returns a job_id, poll get_job, 10–20 minute ETA) that implies how the tool fits into a sequence. However, it gives no criteria for choosing this over fetch or research, and no when-not-to-use conditions, leaving selection guidance to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources