Skip to main content
Glama

textokit_x402_ping

x402 ping: cheapest end-to-end test of an x402 payment on Base. 0.001 USDC per call (x402, Base); an unpaid call returns the x402 payment requirements. Free sample: textokit_sample.

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

Input Schema

NameRequiredDescriptionDefault
echoNoOptional text echoed back (up to 200 characters).
payment_signatureNoOptional, legacy: base64 x402 v2 payment payload. Preferred: params._meta["x402/payment"]. Never a private key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional base64 x402 v2 payment payload for the requirements of a prior unpaid call. Never a private key."New value: +"Optional, legacy: base64 x402 v2 payment payload. Preferred: params._meta[\"x402/payment\"]. Never a private key."
  2. Changed1 schema field changed
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional. Base64 x402 v2 payment payload signed by YOUR wallet for the requirements returned by a previous unpaid call. Never a private key."New value: +"Optional base64 x402 v2 payment payload for the requirements of a prior unpaid call. Never a private key."
  3. First observed

TDQS

A4/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 does well: it discloses the per-call price and currency (0.001 USDC), the payment rail (x402 on Base), and crucially that an unpaid invocation returns the x402 payment requirements rather than failing. It omits rate limits and the shape of a successful paid response, which keeps it below a 5.

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 clauses plus a pointer sentence, with the core purpose and price front-loaded. Every element — price, unpaid-call behavior, free alternative — is actionable and none is 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?

For a paid, annotation-free tool with no output schema, it covers the essentials an agent needs to invoke it correctly: cost, protocol, the unpaid-call discovery path, and a free alternative. Only the successful response shape (echo/pong) is left implicit, a minor gap given `echo` is documented in the schema.

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%, so both `echo` and `payment_signature` are already documented, including the preference for params._meta["x402/payment"] over the legacy field. The description adds no parameter-level detail beyond the payment-model framing, 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 names a specific operation (a ping / end-to-end x402 payment test) on a specific resource (x402 payment on Base) and states its distinguishing trait: it is the cheapest such test at 0.001 USDC. That differentiates it from siblings like textokit_how_to_pay and textokit_x402_adoption, though it never names them explicitly.

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 states the condition for use (testing an x402 payment end-to-end) and offers an explicit alternative for the free case: "Free sample: textokit_sample." It also tells the agent that an unpaid call is a valid discovery step that returns payment requirements. It stops short of saying when NOT to use this versus textokit_how_to_pay.

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.