Skip to main content
Glama

Inspect x402 Contract

x402_contract
Read-onlyIdempotent

Inspect the canonical x402 payment contract. Returns network, USDC asset, payTo, headers, and the rule for resolving fresh target requirements. FREE.

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": "x402_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds two genuine behavioral facts not in the annotations: the operation is FREE (no cost/spend implications, relevant given a sibling named spend_gate_check) and it is the authoritative "canonical" source. It stops short of saying whether the returned rule is static or network-dependent, which matters for a reference tool.

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?

Two sentences, zero waste, and the most decision-relevant facts — what it inspects, what it returns, and that it is free — are front-loaded. The "FREE." fragment is terse but deliberately so and reads clearly as a cost signal.

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?

With no parameters and no output schema, the description sensibly substitutes an enumeration of returned fields (network, USDC asset, payTo, headers, resolution rule), which is exactly the right compensation. Completeness would be higher if it clarified what a "fresh target requirement" rule actually means in practice, since that phrase is the most load-bearing and least explained part.

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?

The tool takes zero parameters, so there is no parameter semantics to clarify and the description is not expected to carry any. Baseline 4 applies: nothing is missing on this dimension.

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?

"Inspect the canonical x402 payment contract" pairs a specific verb with a specific resource and enumerates what the inspection yields (network, USDC asset, payTo, headers, resolution rule). That is far more than a restatement of the name. It does not explicitly differentiate itself from any sibling, but none of the listed siblings appear to touch the x402 contract, so the omission is low-cost rather than a real ambiguity.

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?

There is no explicit when-to-use or when-not-to-use statement and no prerequisites or alternatives named. Usage is only implied — "the rule for resolving fresh target requirements" hints this is a reference lookup you consult before constructing a payment target, but the agent must infer that sequencing itself.

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