Skip to main content
Glama

PayAPI Market

by market.payapi
OverviewDiscussionsAdmin

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.

Input Schema

NameRequiredDescriptionDefault
limitNo
networkNoOnly 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`.
categoryNoExact category name. Call with no category first to see the valid values.
verified_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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`."
  2. 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"
+}
  3. 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 readOnly/idempotent/openWorld/destructive=false, yet the description adds genuinely new information: the tool is free and spends nothing, and by default only settlement-verified listings are returned unless verified_only is false. That default-behavior disclosure is beyond both the annotations and the bare schema default.

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?

Three short sentences, each carrying a distinct fact (scope, filter behavior, cost/safety). Front-loaded with the primary action and zero filler.

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 four-parameter, no-required-arg list tool with no output schema, the description covers the selection semantics an agent needs. The only gap is pagination/limit handling, which is undocumented in both the schema and the description.

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 50%: network and category are described in-schema, while limit and verified_only are not. The description partially compensates by explaining verified_only's effect and the category-omission behavior, but says nothing about limit or paging. Baseline 3 for mid coverage.

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 ('Browse the live catalogue') plus the optional scoping dimension (one category). It is clearly a listing tool, but it never distinguishes itself from the sibling search_apis, which an agent could easily confuse it with.

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 'unless verified_only is false' give implied usage for the filters, but there is no guidance on when to pick this over search_apis or get_api. The agent must infer the boundary itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PayAPI Market toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources