Skip to main content
Glama

agent-exec

Check a 402 quote against what you expected before you sign it (paid, x402)

check_counterparty

PAID: check an x402 quote before you pay it: payee, resource, network, asset and price graded against what you expected. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply. Price: $0.0100 USDC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_counterparty"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimNoWhat you believed before you asked: the URL you requested, and optionally the payee, network, asset and ceiling you agreed to.
quoteNoOne accepts[] entry out of the 402 you received, verbatim. Every field optional: an absent one is a finding.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description goes well beyond by disclosing that the tool is paid, the exact price ($0.0100 USDC), the accepted networks, the payment header location, the free feedback channel, and the fact feedback is read daily without individual replies. That is exactly the context an agent needs before spending money.

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

Conciseness4/5

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

Front-loaded with the paid status and the core action, then the payment mechanics, then feedback, then price. Dense but nearly every clause carries information; the parenthetical network list is the only mildly bulky element.

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 two-object nested schema with no output schema, the description covers the payment loop, the cost, and the fact that results are graded against the claim. It stops short of describing the shape of the grading result, but the operational essentials are all present.

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 100% and the nested claim/quote objects are already documented field by field, including 'an absent one is a finding'. The description restates the graded fields but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

Names a specific verb and resource — checking an x402 402 quote — and enumerates exactly what gets graded (payee, resource, network, asset, price) against the caller's expectations. That is clearly distinct from generic siblings like check_url or check_address.

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?

States the decisive timing ('before you pay it') and then walks the two-step flow: an unpaid call returns the price, then you attach payment in _meta['x402/payment'] and call again. No sibling alternative is named, but the when-to-use condition is unambiguous.

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.