Skip to main content
Glama

textokit_how_to_pay

How to pay a tool with x402 (HTTP 402 or the x402 MCP transport) from your own wallet, and the local npm alternative that signs for you. Free.

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_how_to_pay"
  }
}

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?

With no annotations, the description must carry the behavioral burden, and it does disclose that the call is free and that two payment routes plus a local npm signer are covered. It does not clarify that this returns explanatory content rather than performing a payment, nor what form the response takes, which matters for an agent deciding whether to invoke it mid-task.

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 with the topic and scope front-loaded, followed by the 'Free.' qualifier. No filler, nothing to trim.

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-parameter, no-output-schema documentation tool, the description covers both payment transports and the npm alternative, which is enough for an agent to know what the call yields. It stops short of saying the return value is instructional text or how detailed that text is, a minor gap.

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, so the baseline is 4; the schema is empty and fully described. There is nothing for the description to compensate for on this dimension.

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 topic (paying a tool with x402 via HTTP 402 or the x402 MCP transport) and mentions the npm alternative, so an agent can tell this is an instructional/lookup tool rather than a payment action. It does not explicitly differentiate itself from siblings like textokit_x402_ping or textokit_x402_adoption, leaving overlap ambiguity.

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?

'Free.' signals that calling this tool carries no cost, which implicitly answers one selection question. However, there is no explicit statement of when to call this versus the other x402-related siblings (ping, adoption, receipts), so the agent must infer usage from the topic alone.

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.