Skip to main content
Glama

probe_x402

Decode any x402 endpoint's price, network, asset and payTo without paying it. $0.01 USDC on Base (x402).

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": {
      "url": "<url>"
    },
    "name": "probe_x402"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 it discloses two important behaviors: the operation is non-charging/inspection-only, and invoking it costs $0.01 USDC on Base. It does not cover auth requirements, whether it requires network reachability to the target endpoint, or what happens on a non-x402 URL.

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 short sentences, zero filler, with the capability front-loaded and the cost disclosure trailing where it is easy to find. Every clause carries distinct information.

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 output schema and no annotations, the description usefully enumerates the fields returned (price, network, asset, payTo) and the cost of the call, which is enough for an agent to decide and invoke correctly. The only gap is failure behavior for invalid or non-x402 URLs.

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 coverage is 0% for the single `url` parameter, so the description must compensate; "any x402 endpoint" implies the parameter is the endpoint URL, but no format, scheme, or validation expectations are given. It adds only marginal meaning beyond the bare required string in the schema.

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?

Specific verb ("Decode") plus a precisely enumerated resource ("x402 endpoint's price, network, asset and payTo"), with an explicit scope qualifier ("without paying it"). This is clearly distinguishable from siblings like eth_price, fetch_page, or wallet_balances, which operate on different resources.

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?

The phrase "without paying it" establishes a clear use context: inspect an x402 endpoint's terms before committing to a payment. It does not name an alternative tool or state when not to use it, so it falls short of full 5-level routing guidance.

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