Skip to main content
Glama

Agoranome buyer checks and market data

Payment test

ping
Read-only

x402 test payment: can this wallet pay an x402 API? A paid call of a fraction of a cent in USDC on Base or Solana that returns a signed receipt, proof that the wallet, its spending limit and its x402 client (an AgentCore payments session, a CDP or Privy wallet, or any other client) complete a real paid call end to end, plus what Agoranome already knows about the wallet. For an agent's first payment, before it buys anything bigger. Price: $0.001 in USDC per call, paid with x402 inside the tool call. Same price over HTTP, which any x402 client pays without MCP (prefer it if your client pays HTTP 402s): GET https://api.agoranome.com/v1/machine/ping. Or send a Skyfire pay or kya-pay token in the kyapay-token header (or in this tool's kyapay-token argument), and this tool charges $0.001 to it. Failed calls aren't charged.

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

Input Schema

NameRequiredDescriptionDefault
kyapay-tokenNoA Skyfire pay or kya-pay token made for Agoranome's service, from a client that can't set the kyapay-token header. Leave it out when paying with x402 or the header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / kyapay-token
      Added value: +{
      +  "description": "A Skyfire pay or kya-pay token made for Agoranome's service, from a client that can't set the kyapay-token header. Leave it out when paying with x402 or the header.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With only readOnlyHint and openWorldHint supplied, the description carries real weight: it discloses the exact price ($0.001 USDC on Base or Solana), that charging happens inside the tool call, that failed calls are not charged, what the response contains (a signed receipt plus what Agoranome knows about the wallet), and the alternative auth header. An agent knows the cost and risk profile before invoking.

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

Conciseness3/5

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

The core purpose and price are front-loaded, but the body is one long run-on sentence dense with parentheticals, a raw URL, and cross-channel marketing copy about the HTTP alternative. Most of the information earns its place, yet the packaging makes it harder to scan than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter tool with no output schema, it covers everything an agent needs: what is being tested, the price and payment rails, failure billing behavior, and the content of the returned receipt. Nothing material is left to inference.

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 100% and the single kyapay-token parameter is already fully documented in the schema, including the instruction to omit it when paying with x402 or the header. The description restates that a token can go in the argument, adding little beyond what the schema provides, so the baseline of 3 applies.

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 opens by identifying this as an x402 test payment that verifies whether a wallet can complete a real paid API call, which is a specific and concrete purpose beyond the opaque name 'ping'. It does not explicitly differentiate itself from siblings like spend_audit or buyer_check, but the function is unambiguous on its own.

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?

It gives explicit timing advice ('For an agent's first payment, before it buys anything bigger') and names transport/auth alternatives: the HTTP 402 endpoint and the Skyfire pay/kya-pay token. What it lacks is any framing against sibling tools, so the when-to-use guidance is strong in absolute terms but not comparative.

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.