Skip to main content
Glama

Search the PayAPI Market catalogue

search_apis
Read-onlyIdempotent

Free-text search across the live catalogue. Matches listing name, description, category and provider name. 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

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": {
      "query": "<query>"
    },
    "name": "search_apis"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWhat you are looking for, e.g. "uk property" or "sanctions screening".
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`.
subcategoryNoTrading and market data job. One of: market-and-price-data, derivatives-and-options, risk-and-hedging, on-chain-analytics, token-verdicts-and-signals. Omit for no extra filter. This is a keyword group, not a database category.
verified_onlyNoRestrict to settlement-verified listings. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / subcategory
      Added value: +{
      +  "description": "Trading and market data job. One of: market-and-price-data, derivatives-and-options, risk-and-hedging, on-chain-analytics, token-verdicts-and-signals. Omit for no extra filter. This is a keyword group, not a database category.",
      +  "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.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior; the description adds that the search spends nothing, defaults to settlement-verified listings, and explains tracked_url/base_url result semantics and PayAPI's 0% role. It stops short of rate limits, auth requirements, or exhaustive result behavior.

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 and most sentences are short, but the tracked_url/base_url passage is repetitive and awkward ('Call tracked_url... That is the URL to call... It is the PayAPI path...'). It is understandable but not tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the core search behavior plus important result-field semantics for tracked_url/base_url, but with no output schema the description should more fully explain result shape, pagination/limit behavior, and search operators. Adequate but incomplete for an open-world catalogue search.

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 80%, so most parameters are already documented. The description reinforces verified_only's default and the matched fields, but adds no detail on limit, network, subcategory semantics, or query syntax beyond what the schema provides.

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 ('Free-text search across the live catalogue') and identifies the fields matched. It is distinguishable from a list or single-item lookup, but does not explicitly route against sibling tools such as list_apis or get_api.

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?

Provides context for a free-text catalogue search and explains the verified_only default, but gives no explicit when-to-use or when-not guidance versus list_apis, get_api, or search_agents. The tracked_url/base_url note is post-result guidance rather than tool-selection guidance.

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