Skip to main content
Glama

Agent Data Tools

by io.github.Nutshell2000
OverviewDiscussionsAdmin

Ping, x402 payment test: a minimal paid call to test that an x402 payment settles

ping
Read-only

A paid round-trip check: returns pong and the server time. Use to test that an x402 wallet, client or MCP setup can pay and receive a result. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

Input Schema

NameRequiredDescriptionDefault
onlyNoOptional: comma-separated top-level result keys to keep, for a smaller answer (for example only=price,symbol); unknown keys are ignored and an empty match returns the full result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / only / description
      Previous value: -"Optional: comma-separated top-level result keys to keep, for a smaller answer (for example only=fastestFee,halfHourFee); unknown keys are ignored and an empty match returns the full result"New value: +"Optional: comma-separated top-level result keys to keep, for a smaller answer (for example only=price,symbol); unknown keys are ignored and an empty match returns the full result"
  2. Changed1 schema field changed
    • addedInput schema / properties / only
      Added value: +{
+  "description": "Optional: comma-separated top-level result keys to keep, for a smaller answer (for example only=fastestFee,halfHourFee); unknown keys are ignored and an empty match returns the full result",
+  "type": "string"
+}
  3. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses pricing ($0.01/call via USDC or card key), a 25-call free tier, that failed calls are not charged, and that each call is billed so repeats are not free. That last point usefully explains the idempotentHint=false annotation rather than contradicting it, and 'reads or computes only and changes nothing' aligns with readOnlyHint=true.

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?

Three tight sentences, front-loaded with the return behavior and then the use case and billing. There is minor repetition around payment ('paid round-trip', 'each call is charged'), but nothing is padding.

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 zero-required-parameter diagnostic tool with no output schema, it covers return values, billing, and side-effect freedom. The only gap is that the 'only' filter is left entirely to the schema, which is acceptable given full coverage.

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 single optional 'only' filter is fully documented in the schema, so the baseline of 3 applies. The description adds no extra detail about the parameter or typical key values.

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?

States a specific verb and resource ('paid round-trip check: returns pong and the server time') and immediately frames the tool as a payment-settlement test, which separates it from the free 'echo' sibling in the list. An agent knows both what comes back and why this tool exists.

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?

Explicitly says to use it 'to test that an x402 wallet, client or MCP setup can pay and receive a result', which is a clear usage trigger. It never names the obvious alternative (the free 'echo' tool) or says when not to spend money, so the routing guidance is implied rather than complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Data Tools toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources