Skip to main content
Glama

List the PayAPI Market catalogue

list_apis
Read-onlyIdempotent

Browse the live catalogue, optionally filtered to one category. Omit category for everything. Returns settlement-verified listings only unless verified_only is false. 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

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_apis"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
networkNoOnly listings that accept USDC on this network: base, solana, algorand, avalanche, or a CAIP-2 id. Omit for all. Each listing reports its rails in `networks`.
categoryNoExact database category, or "Trading and market data" for the keyword group. That group is not stored on the row. Call with no category first to see the database categories.
subcategoryNoOne job inside Trading and market data: market-and-price-data, derivatives-and-options, risk-and-hedging, on-chain-analytics, token-verdicts-and-signals. Omit for no extra filter.
verified_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Exact category name. Call with no category first to see the valid values."New value: +"Exact database category, or \"Trading and market data\" for the keyword group. That group is not stored on the row. Call with no category first to see the database categories."
    • addedInput schema / properties / subcategory
      Added value: +{
      +  "description": "One job inside Trading and market data: market-and-price-data, derivatives-and-options, risk-and-hedging, on-chain-analytics, token-verdicts-and-signals. Omit for no extra filter.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / network / description
      Previous value: -"Only listings that accept USDC on this network: base, solana, algorand, or a CAIP-2 id. Omit for all. Each listing reports its rails in `networks`."New value: +"Only listings that accept USDC on this network: base, solana, algorand, avalanche, or a CAIP-2 id. Omit for all. Each listing reports its rails in `networks`."
  3. Changed1 schema field changed
    • changedInput schema / properties / network / description
      Previous value: -"Only listings that accept USDC on this network: base, solana, or a CAIP-2 id. Omit for all. Each listing reports its rails in `networks`."New value: +"Only listings that accept USDC on this network: base, solana, algorand, or a CAIP-2 id. Omit for all. Each listing reports its rails in `networks`."
  4. Changed1 schema field changed
    • addedInput schema / properties / network
      Added value: +{
      +  "description": "Only listings that accept USDC on this network: base, solana, or a CAIP-2 id. Omit for all. Each listing reports its rails in `networks`.",
      +  "type": "string"
      +}
  5. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so safety is covered; the description still adds cost transparency ("Free and read-only; spends nothing") and the important default that unverified listings are hidden. It also explains the tracked_url/base_url relationship the agent must understand to actually use results, though the wording is terse and slightly cryptic.

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 purpose and defaults, then the tracked_url guidance, with little filler. The tracked_url/base_url block is fragmented ("That is the URL to call. It is the PayAPI path...") and slightly hard to parse, costing it a point.

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 usefully explains how returned listings should be used (tracked_url vs base_url) and the fee model. Remaining gaps are minor: no mention of result ordering or what happens as limit (max 100) is reached.

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?

Schema coverage is 60% and verified_only/limit have no schema descriptions, so the description carries real weight: it explains verified_only's default meaning (settlement-verified only) and category's omit-for-everything behavior. network, subcategory, and limit semantics are left to the schema, which handles them adequately.

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?

"Browse the live catalogue, optionally filtered to one category" gives a specific verb (browse) plus resource (catalogue) and states the default scope. It implicitly distinguishes browsing from get_api/search_apis by name contrast, but never explicitly says how it differs from search_apis.

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?

"Omit category for everything" and "Returns settlement-verified listings only unless verified_only is false" give usage rules for two parameters, which is helpful. However there is no explicit when-to-use guidance relative to the siblings (search_apis, get_api, search_agents), so the agent must infer the browse-vs-search split.

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