Skip to main content
Glama

Pay-per-call APIs (x402)

list_paid_apis
Read-onlyIdempotent

List this server's pay-per-call HTTP APIs that agents can buy with USDC via x402 (Base, Polygon or Solana), with URL, price, input schema and an example: Argentina dolar quotes (oficial, blue, MEP, CCL, cripto, tarjeta) and FX exchange rate (0.002), Argentine CUIT/CUIL and CBU/CVU validators and Argentine phone normalizer to E.164 + WhatsApp link (0.01), web page SEO/security audit (0.02) and the landing page generator (0.25). Invalid input is never charged. Free to call; returns JSON text.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds genuinely new behavioral facts: calling is free, billing is per-call in USDC on Base/Polygon/Solana, and invalid input is never charged. It also states the response is JSON text with URL, price, input schema and an example per entry — a real disclosure beyond the annotations, though it doesn't cover the payment handshake or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, which is good, but the sentence then becomes a long catalog dump of every API and its price. That pricing detail belongs to the return value rather than to the decision of how to invoke a zero-parameter tool, and the run-on structure makes it harder to scan.

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?

With no output schema, the description carries the burden of describing return content and does so by naming the per-entry fields (URL, price, input schema, example) and the format (JSON text). Combined with the rich annotations, an agent has enough to call it correctly; only the exact envelope shape and any pagination remain unstated.

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 of 4 applies; there are no parameter semantics for the description to explain. The price figures quoted in the description would only matter to a caller, not as inputs.

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?

States a specific verb and resource — list this server's pay-per-call HTTP APIs purchasable with USDC via x402 — and enumerates the catalog contents, which makes clear it returns metadata about APIs rather than executing them. Siblings are only referenced indirectly (the landing page generator is listed as a catalog entry, not as a pointer to generate_landing_page), so differentiation is implied rather than explicit.

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?

Usage is implied: an agent should call this to discover what paid APIs exist and what they cost before invoking one. There is no explicit when-not-to-use guidance and no named alternative (e.g., get_service_info for server-level metadata), so routing between the three siblings is left 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