Skip to main content
Glama

axveritas_verify_scrape

Zero-trust 2-bot x402 verification relay (1% toll, $0.001 min) on Base Mainnet.

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": {
      "target_worker_endpoint": "<target_worker_endpoint>",
      "target_scrape_url": "<target_scrape_url>",
      "bounty_usdc": "<bounty_usdc>",
      "required_keys": "<required_keys>"
    },
    "name": "axveritas_verify_scrape"
  }
}

Input Schema

NameRequiredDescriptionDefault
bounty_usdcYes
required_keysYes
target_scrape_urlYes
target_worker_endpointYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / bounty_usdc / description
      Removed value: -"Escrow bounty in USDC"
    • removedInput schema / properties / target_scrape_url / description
      Removed value: -"URL to scrape"
    • removedInput schema / properties / target_worker_endpoint / description
      Removed value: -"Worker POST endpoint"
  2. First observed

TDQS

C2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it only discloses pricing (1% toll, $0.001 minimum) and chain context (Base Mainnet). It omits critical behavior: that calling it likely spends USDC from a bounty, whether payments are irreversible, what the 'required_keys' gate does, what authorization is needed, and what the relay returns.

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

Conciseness3/5

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

It is a single short sentence with no filler, which is good structurally, but the brevity comes at the cost of clarity and the jargon-dense phrasing ('2-bot x402 verification relay') is not front-loaded around the actual action.

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

Completeness1/5

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

For a four-required-parameter tool with no annotations and no output schema, involving an on-chain payment and a required-keys authorization gate, one marketing-style sentence is grossly insufficient. An agent lacks nearly everything needed to invoke this correctly and safely.

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?

Schema description coverage is 0% across four required parameters, so the description must compensate and does not. The only tangential link is the '$0.001 min' hint relating loosely to bounty_usdc; target_worker_endpoint, target_scrape_url, and required_keys receive no explanation whatsoever.

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

Purpose2/5

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

The description identifies the tool as an 'x402 verification relay' on Base Mainnet, which hints at a verification function, but it never states a concrete verb+resource action (e.g., 'verify a worker's scrape result and settle a bounty'). Terms like '2-bot' and 'zero-trust relay' are unexplained jargon, and nothing distinguishes it from the sibling axveritas_scrape_verified.

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

Usage Guidelines2/5

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

No when-to-use guidance is given at all. The agent cannot tell from this text whether this tool should be chosen over axveritas_scrape_verified, what preconditions exist, or in what part of a workflow verification belongs.

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