Skip to main content
Glama

AutoPay

verify

Queue a claim/company/URL verification ($0.08). 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": {
      "claim": "<claim>"
    },
    "name": "verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 well: it discloses price ($0.08), both auth paths (X-PAYMENT x402 USDC on Base or prepaid API key), the 202 status code, job_id in the response, and a 10–20 minute latency plus the polling next step. It does not cover what happens on failed verification, whether charges are refunded, or rate limits, so it falls short of a 5.

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 compact sentences, front-loaded with the action and cost, followed by payment options and the async contract. Every clause adds information an agent needs; there is no repetition of the name or filler.

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 single-parameter asynchronous job-submission tool with no output schema and no annotations, the description supplies the payment model, response code, identifier, latency, and follow-up tool. Only the failure/refund behavior and expected result shape are left unstated.

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

Parameters4/5

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

Schema coverage is 0% for the single required 'claim' parameter, so the description must compensate, and it does partially by indicating the input may be a claim text, a company, or a URL. It does not state format limits or how to pass a company versus a claim, which would be needed for full credit.

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?

The description uses a specific verb ('Queue') and resource ('claim/company/URL verification') and states the outcome (202 + job_id), so the agent knows this starts an asynchronous verification. It does not explain what 'verification' actually means for a claim (fact-check? domain check?), which leaves the semantic scope partly ambiguous. Sibling differentiation is implicit through the explicit pointer to get_job for polling.

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?

It gives a clear operational path: queue here, then 'poll get_job', with a stated ETA of 10–20 minutes, which tells the agent this is not a synchronous lookup. It does not state when to prefer this over a synchronous sibling such as fetch or search, so the exclusion side of the guidance is missing.

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