Skip to main content
Glama

AutoPay

research

Queue a short cited brief ($0.30). 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": {
      "question": "<question>"
    },
    "name": "research"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses the price ($0.30), the two payment paths (x402 USDC on Base or prepaid API key), that the call is asynchronous and returns 202 with a job_id, and the expected 10–20 minute latency. That is exactly the behavioral context an agent needs before committing money and switching to a polling loop.

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 short clauses, front-loaded with the action and cost, then payment, then return contract, then follow-up. Every sentence carries information the agent needs; nothing is padding.

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?

Coverage is strong for an async, paid tool with no output schema: cost, auth, response code, job identifier, latency, and the exact next call are all present. The remaining gap is failure behavior — what happens if payment fails or the job errors, and whether the charge is incurred on failure — which matters given the monetary cost.

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 description coverage is 0% for the single required parameter, so the description must compensate; it adds only indirect meaning via "short cited brief," implying the question should be scoped to something answerable in a brief. It says nothing about question length, formatting, or how ambiguity is handled. The parameter is largely self-evident from its name, so this is a moderate gap rather than a critical one.

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 short cited brief" gives a specific verb (queue, i.e. asynchronous submission) and a concrete resource with a defined output shape (short, cited brief), which separates it from siblings like get_job, fetch, search and verify. It stops short of naming an explicit alternative for the synchronous-lookup case, so it lands just below the top mark.

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 description gives clear operational context: this is the entry point, and the follow-up step is "poll get_job," which routes the agent to the correct sibling. It does not state when NOT to use it (e.g. when the answer is already available via search/fetch), so there is no exclusion guidance.

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