Skip to main content
Glama

textokit_x402_adoption

Base USDC receipt reconciliation and duplicate detection. 0.01 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_adoption"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundleNoJSON string, at most 120000 UTF-8 bytes: {tape:{network:eip1…
sectionNoWhich part of the report to return. overview: headline…overview
operationNoaudit reconciles the supplied bundle; market_stats returns a…
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. Changed2 schema fields changed
    • addedInput schema / properties / bundle
      Added value: +{
      +  "description": "JSON string, at most 120000 UTF-8 bytes: {tape:{network:eip1…",
      +  "maxLength": 120000,
      +  "type": "string"
      +}
    • addedInput schema / properties / operation
      Added value: +{
      +  "description": "audit reconciles the supplied bundle; market_stats returns a…",
      +  "enum": [
      +    "audit",
      +    "market_stats"
      +  ],
      +  "type": "string"
      +}
  3. Changed2 schema fields 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."
    • changedInput schema / properties / section / description
      Previous value: -"Which part of the report to return. overview: headline counts and conclusions; bazaar: network, asset and version shares; sellers: host and wallet concentration plus the Agent402 leaderboard; payers: how many resources have 1, 2, 5 or 10+ unique payers in 30 days; prices: USDC price percentiles; categories: keyword categories; demand: the paid demand radar; all: everything."New value: +"Which part of the report to return. overview: headline…"
  4. First observed

TDQS

B3.4/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 does disclose the most consequential trait: a paid x402 call at 0.01 USDC that returns payment requirements when unpaid. That is real behavioral context an agent cannot infer from the schema. It stops short of stating that the tool is read-only or what the response looks like, but the payment gating is well covered.

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?

Three short sentences, front-loaded with the purpose, then cost/payment mechanics, then the free escape hatch. Every sentence earns its place and there is no filler.

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

Completeness3/5

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

Payment mechanics are covered, but with four parameters, two enums, no output schema, and no annotations, the description omits the operation split (audit vs market_stats) and the required preconditions for supplying a bundle. That leaves a meaningful gap for a tool this configurable.

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 the parameters are already documented, and the description adds no meaning about bundle, section, or the audit/market_stats distinction. The one exception is payment_signature, where the schema itself already notes the legacy vs _meta preference. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Base USDC receipt reconciliation and duplicate detection" is a specific verb+resource framing, but it only describes the audit half of the tool. The schema's operation enum also offers market_stats, which the description never mentions, so an agent reading only the description cannot tell what the tool fully does.

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?

It gives useful routing hints: a free sample is named (textokit_sample) and the unpaid-call behavior is stated. However, there is no guidance on when to use this versus the closely-named sibling textokit_base_usdc_receipts, and no indication of when to pick audit vs market_stats.

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.