Skip to main content
Glama

Paid API finder (x402/MPP), free

Check a pay-per-call API origin

check_x402_origin
Read-onlyIdempotent

Free readiness check of an x402/MPP seller origin you operate or want to evaluate: openapi.json, declared paid operations, whether each answers a valid 402, price parity, MPP realm. Reads public URLs only; pays nothing.

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": {
      "origin": "<origin>"
    },
    "name": "check_x402_origin"
  }
}

Input Schema

NameRequiredDescriptionDefault
originYeshttps://host of the API

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), but the description adds real context beyond them: 'reads public URLs only' (no credentials or auth handshakes) and 'pays nothing' (no wallet spend), which is material for an x402 tool. It does not describe the shape of the resulting report, which is a gap since there is no output schema.

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?

Front-loaded with the value proposition ('Free readiness check') followed by a compact list of checks and a closing two-clause constraint. Every clause carries information; the enumerated list makes the single sentence slightly dense but not wasteful.

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 one-parameter read-only probe with annotations covering safety, the description supplies the checks performed, the no-payment guarantee, and the public-URL scope. The only missing piece is a hint at the returned report structure, 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 coverage is 100% and the single parameter already documents the expected form ('https://host of the API'). The description adds no format, normalization, or path restrictions beyond 'origin', so the schema does the work and baseline 3 applies.

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?

Specific verb plus resource ('readiness check of an x402/MPP seller origin') followed by an enumeration of exactly what is inspected: openapi.json discovery, declared paid operations, 402 validity, price parity, MPP realm. The 'origin you operate or want to evaluate' framing implicitly separates it from the discovery-oriented find_paid_api, but no sibling is named, so the differentiation is inferential 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage contexts — you already have an origin you run, or one you are evaluating — and notes it is free, so no budget consideration gates the call. It stops short of stating exclusions or naming find_paid_api as the alternative when you do not yet have a URL.

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