Skip to main content
Glama

list_endpoints

Discover available paid tools, their USDC prices on Base via x402, and matching HTTP endpoints so agents can choose and call the right API.

Instructions

Free: list paid tools, prices (USDC on Base, x402) and the equivalent HTTP endpoints.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations, so the description carries the burden; it does disclose the important behavioral fact that this call is free while the tools it lists are paid, plus the payment rail (x402, USDC on Base). It says nothing about auth, rate limits, pagination, or ordering of results.

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?

One well-formed sentence with the cost caveat front-loaded and the three returned artifacts enumerated. No filler, though the price-rail detail (x402) may be marginally over-specific for a first-read.

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 zero-parameter, no-output-schema read tool, the description covers cost model, what is returned (tools, prices, equivalent HTTP endpoints), and payment context. Nothing essential to invoking it is missing, though return shape (is it a list? grouped by tool?) is only loosely implied.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies an unfiltered full listing, which is consistent with the empty schema.

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?

Specific verb 'list' with a concrete resource set: paid tools, prices (USDC on Base, x402) and their equivalent HTTP endpoints. An agent can tell this is a discovery/catalog tool rather than an executor, though the name 'list_endpoints' undersells that it also returns pricing.

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

Usage Guidelines2/5

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

The 'Free:' prefix implicitly signals 'call this to discover what's available at no cost', but there is no explicit when-to-use, when-not-to-use, or pointer to any alternative (e.g. mcp_inspect). The agent must infer the discovery role.

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