Skip to main content
Glama

X402 recommend

x402_recommend
Read-onlyIdempotent

Recommend verified x402 paid APIs, 62k+ MCP servers, and 2.5k+ OpenAPIs for any agent goal, with live 402 payment-term verification. $0.008 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "goal": "<goal>"
    },
    "name": "x402_recommend"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYestask description (3-240 chars)
kindNoall (default), x402, mcp or openapi
chainNooptional network filter (base, arc, solana, ethereum, bnb, x1...)
limitNo1-20
probeNotrue (default) or false
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
maxPriceNooptional max USD price

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint true and destructive false, yet the description adds material context the annotations cannot: a concrete price ($0.008 per call), accepted settlement assets and chains (USDC on Arc/Base/Solana, XNT on X1), and the fact that payment is verified live and settled inside the second call. That is exactly the kind of cost and authorization disclosure an agent needs before invoking. The only soft spot is the tension between readOnlyHint=true and a call that completes a purchase, which the description surfaces but the annotation does not reconcile.

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 sentences, front-loaded with purpose, then pricing, then the call protocol — each sentence carries distinct information and nothing is repeated. Slightly dense phrasing ('$0.008 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1)') but no wasted text.

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 7-parameter, no-output-schema discovery tool, the description covers the essentials an agent needs to call it correctly: what it returns conceptually (verified recommendations), what it costs, and how payment gating works. The main omission is any hint about the shape or size of the recommendation payload (e.g., what fields a result carries), which matters more here because no output schema exists.

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 schema already documents goal, kind, chain, limit, probe, payment, and maxPrice, making 3 the baseline. The description reinforces the meaning of `payment` by tying it to a two-step sign-then-submit flow, but adds no format, default, or constraint detail beyond what the schema fields already say.

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 with a specific verb and resource set: it recommends verified x402 paid APIs, MCP servers, and OpenAPIs, and adds live 402 payment-term verification. An agent immediately knows this is a discovery/recommendation tool rather than an inspection or stats tool. It stops short of naming any sibling (e.g., x402_inspect or x402_bazaar_rank) to sharpen the boundary, so it earns a 4 rather than a 5.

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?

The invocation protocol is spelled out explicitly: call once without `payment` to get terms, sign them with your own wallet, then call again with `payment`. That is actionable when-to/how-to guidance with a clear prerequisite (a wallet). It does not, however, state when to prefer this tool over the many adjacent discovery/inspection siblings, leaving that choice to inference.

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.

Resources