Skip to main content
Glama

Get one PayAPI Market listing

get_api
Read-onlyIdempotent

Fetch a single live listing by its id or slug, including base_url, price range, network and verification state. payment_verified is true if at least one route was paid; verified_routes names each paid route with its on-chain receipt. test_payment_usdc is the test payment, not the per-call price. amount_usdc is deprecated and has the same value; it is the verification test payment, not the price. The per-call price is price_min and price_max. Also returns a reliability object: score (0 to 100 or null), band (strong, established, thin, caution or unscored) and computed_at. Reliability is a running score from paid verifications, health history and payTo integrity, not a star rating and not a guarantee; unscored means it has not been computed for that listing yet. Method: https://payapi.market/how-an-agent-finds-payapi. Returns the listing whether or not it is verified, and reports payment_verified honestly. Free and read-only; spends nothing. Call tracked_url when a listing includes it. That is the URL to call. It is the PayAPI path to the provider host in base_url. base_url stays the provider address. PayAPI takes 0% and does not change who is paid.

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": {
      "id": "<id>"
    },
    "name": "get_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesListing uuid or slug, as returned by search_apis or list_apis.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description still adds substance: 'Free and read-only; spends nothing,' that it returns unverified listings too and 'reports payment_verified honestly,' and that PayAPI takes 0% and does not alter who is paid. It stops short of describing failure behavior when an id is unknown.

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?

Purpose is front-loaded, but the body is bloated and repetitive: 'not the per-call price' / 'not the price' appears three times, and the reliability and 0%-fee asides read as marketing copy rather than call-relevant detail.

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 return-value semantics and does so well, disambiguating the confusing test_payment_usdc / amount_usdc / price_min-max fields and explaining the reliability object's score, bands, and 'unscored' meaning. Only edge cases such as not-found behavior are unaddressed.

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 already states the parameter is a 'Listing uuid or slug, as returned by search_apis or list_apis.' The description's 'by its id or slug' merely restates that, adding no format or lookup nuance.

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?

Starts with a specific verb and resource: 'Fetch a single live listing by its id or slug,' and enumerates the payload (base_url, price range, network, verification state). The word 'single' plus the slug/id lookup cleanly separates it from the list/search siblings.

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?

There is real operational guidance ('Call tracked_url when a listing includes it. That is the URL to call'), but that governs what to do with the result, not when to pick this tool over search_apis or list_apis. The choice of this tool is only implied by 'a single live listing by its id or slug.'

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