Skip to main content
Glama

Antigravity x402 & MCP Gateway

list_x402_pricing_and_wallets

Free discovery tool returning all paid x402 endpoints, USDC prices, supported chains (Base eip155:8453 & Polygon eip155:137), and sample payloads.

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

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?

No annotations are supplied, so the description carries the full burden. It usefully discloses that access is free (meaningful in an x402 context where endpoints are paid) and that the result is a complete catalog rather than a filtered subset. It does not state whether the data is live or static, whether any auth or rate limit applies, or confirm the read-only/no-side-effect nature.

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?

A single sentence, front-loaded with the key traits (free, discovery) and then the returned contents including chain identifiers. No filler and nothing redundant.

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, no annotations, and no output schema, the description does the necessary work by enumerating what comes back (endpoints, prices, chains, sample payloads). The remaining gap is freshness/liveness of the catalog and any access constraints, which an agent would want to know before treating it as authoritative pricing.

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, which is the baseline-4 case; there is nothing to disambiguate. The description helpfully confirms the no-argument, return-everything model by saying it returns 'all' endpoints.

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 names a concrete resource set: all paid x402 endpoints, USDC prices, supported chains with explicit CAIP-2 IDs, and sample payloads. That is far more specific than the tool name alone and clearly separates it from the analysis/audit siblings. It stops short of a 5 because it never frames itself against any other tool.

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?

Only implied guidance: calling it a 'free discovery tool' signals it is an entry point to be used before paying for or invoking an endpoint, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent can infer the role but must reason about it.

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.