Skip to main content
Glama

x402-mcp

by io.github.kwizzlesurp10-ctrl

Discover x402 services

x402.discover
Read-onlyIdempotent

Discover paid HTTP APIs in the x402 Bazaar via the facilitator catalog. Call this first to find a resource URL, then x402.probe and x402.pay_and_fetch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of catalog entries to return. Default 20. Range 1–100.
queryNoOptional Bazaar search substring. Example: 'weather' or 'image'. Omit to list recent paid HTTP services.
agent_idNoOptional agent identity for quota accounting. Example: 'agent-42'. Omit to use the anonymous free-tier id.
max_price_usdcNoOptional USDC price ceiling. Example: 0.05. Omit to include any listed price.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety aspects: readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds useful behavioral context by identifying the facilitator catalog and the required sequence. There is no contradiction between the description and annotations.

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?

The description is two sentences with no filler. The first sentence defines the purpose, and the second explains the workflow position. It is front-loaded and easy to process.

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 simple, fully-described, optional-parameter discovery tool, the description plus schema and annotations cover invocation well. It could optionally say a bit more about result ordering or catalog scope, but that is not necessary for correct use. A minor gap, not a deficiency.

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 each parameter already has a clear description, default value, and example. The tool description itself does not add parameter-level meaning, which is acceptable because the schema carries the full burden.

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

Purpose5/5

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

The description states a specific verb and resource: “Discover paid HTTP APIs in the x402 Bazaar via the facilitator catalog.” It also explains the expected first-step role by saying this tool finds a resource URL to feed into x402.probe and x402.pay_and_fetch, which clearly differentiates it from the related siblings.

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 description gives explicit when-to-use guidance: “Call this first to find a resource URL, then x402.probe and x402.pay_and_fetch.” It clearly frames the recommended ordering. It does not enumerate exclusions or alternatives, but the workflow context is strong enough for an agent to orient correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All x402-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation3/5

The namespaces help, but there is real overlap in purpose: city.check with x402.pay_and_fetch, city.sample with x402.probe, and multiple tools that verify a payment and then activate, credit, or settle something. The descriptions clarify which resource is being paid for, but tool names alone leave room for misselection.

Naming Consistency4/5

Nearly every tool uses a lower-case dotted namespace.action pattern, making the set easy to scan. Some command parts are inconsistent, though: x402.networks, pulse.base, and commerce.credits_requirements read as nouns rather than actions, so the style is mostly but not fully uniform.

Tool Count3/5

Nineteen tools is in the heavy range, and they span many subsystems: x402, city, commerce/quotas, swarm, ops, and Base network metrics. The number is not extreme, but the server feels like multiple product surfaces bundled under one MCP rather than a tightly scoped toolset.

Completeness4/5

The x402 lifecycle is well covered: discover, probe, pay, fetch, verify, sell, and settle, plus supportive commerce and city workflows. Notable gaps are refunds/quota-balance checks, seller resource update/removal, and invoice-like management for Stripe/card purchases, but none blocks the object workflows.

Resources