Skip to main content
Glama

List paid endpoints

list_paid_endpoints
Read-onlyIdempotent

x402-priced endpoints with the price per call the hub read from their own 402 answers, the network and asset they settle in, and how that price moved over time. Use it to compare what a capability costs across providers or to find the cheapest; search_agents is better for finding a capability by what it does. Filters for price ceiling and origin. Read-only, no account; nothing is paid by reading. Returns the endpoints with resource URL, price, asset, network and price history.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMost endpoints to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Most endpoints to return"
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit / minimum
      Added value: +0
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds value they do not cover: no account required, no payment incurred by reading, and the provenance of the price data (read from each provider's own 402 answers). The one blemish is the claim of "filters for price ceiling and origin," which no schema field supports.

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?

Two sentences, no filler, with usage and alternative routing front-loaded before the return-field list. The opening sentence is a dense attribute fragment rather than a verb-led statement, and the trailing return-field enumeration is slightly over-packed for a one-parameter tool.

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 enumerates the returned fields (resource URL, price, asset, network, price history), and it covers safety and access prerequisites for a simple read tool. It omits pagination/default-limit behavior and overstates the available filters, which is the main remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single `limit` parameter, so the baseline would be 3, but the description never mentions `limit` or its default behavior and instead advertises price-ceiling and origin filters that do not exist in the input schema. That actively misdirects the agent about what it can pass.

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?

The first sentence names the exact resource (x402-priced endpoints) and enumerates the attributes it carries: price per call, its provenance (the hub's read of their 402 answers), settlement network and asset, and price history. The second sentence explicitly contrasts it with search_agents, so an agent can distinguish the two without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives a concrete when-to-use ("compare what a capability costs across providers or to find the cheapest") plus the named alternative and the condition that selects it ("search_agents is better for finding a capability by what it does"). This is an explicit routing rule, not inferred usage.

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.