Skip to main content
Glama

Paid API finder (x402/MPP), free

Find a paid API that answers right now

find_paid_api
Read-onlyIdempotent

Describe what an agent needs (e.g. 'weather alerts', 'sec filings', 'token safety'). Returns pay-per-call HTTP APIs (x402 / MPP) that answered a valid 402 payment request seconds ago, with price, network and payTo, cheapest first. Dead listings are dropped. Free; nothing is paid or stored.

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": {
      "need": "<need>"
    },
    "name": "find_paid_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYesWhat the agent needs, in plain words
max_price_usdNoOptional price ceiling per call in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, so the bar is lower. The description still adds real value beyond them: a freshness guarantee ('answered a valid 402 payment request seconds ago'), a liveness filter ('dead listings are dropped'), ordering ('cheapest first'), and cost/side-effect confirmation ('Free; nothing is paid or stored'). It omits result-count or pagination behavior, which keeps it from a 5.

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?

Two tight sentences with zero filler. The capability and its distinguishing property (freshness) come first, then the return shape and cost guarantee, so an agent gets the essentials from the opening clause.

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 returns, and it does: price, network, payTo, sorted cheapest first. For a two-parameter lookup tool that is close to complete; it does not say how many results come back or what an empty result looks like.

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 both parameters are already documented and the baseline is 3. The description reinforces 'need' by giving three natural-language examples, but adds no new meaning for max_price_usd beyond the schema's 'price ceiling per call in USD'.

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?

States a specific verb and resource ('find paid API'), and immediately narrows it: pay-per-call HTTP APIs (x402/MPP) that answered a valid 402 payment request seconds ago. The example needs ('weather alerts', 'sec filings', 'token safety') make the resource concrete enough that an agent can distinguish it from a generic API directory or the check_x402_origin sibling.

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?

The phrase 'answers right now' and 'Dead listings are dropped' implies the use case (you need a currently live endpoint), and 'Free; nothing is paid or stored' reassures the agent it is safe to call speculatively. But there is no explicit when-to-use/when-not guidance and no named alternative, so the routing decision 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