Skip to main content
Glama

Agent Exchange router

The best live paid endpoint for any need

ask
Read-only

The Agent Exchange router: one question, the best live x402 endpoints for that need, ranked by on-chain payers then price, re-probed hourly. Each answer carries url, method, price_usd, network, payers, settled_usd and the seller page. Free, no signup. To use an answer: GET its url unpaid, read the 402 payment ask, pay the payTo in USDC on Base (x402), retry: delivery at once.

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": {
      "need": "<need>"
    },
    "name": "ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYeswhat you need done: words
limitNo
max_price_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, it discloses the ranking signal (payers, then price), the hourly re-probing freshness guarantee, cost (free), and the exact downstream payment handshake. This is genuinely useful context the schema does not carry. The only tension is openWorldHint=false for a tool that presumably reaches live external endpoints, though the description never explicitly contradicts the annotation.

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?

Densely front-loaded: purpose, ranking, freshness, and return fields come first, with the usage procedure last. Some sentences are crammed with semicolons and colons, but every clause carries information and nothing is padding.

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?

With no output schema, listing the returned fields (url, method, price_usd, network, payers, settled_usd, seller page) is valuable, and the x402 payment flow is explained. However the two optional numeric parameters remain unexplained and no result-set behavior (ranking/paging) is described for the limit parameter.

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 only 33%: 'need' is documented while limit and max_price_usd are not described in the schema. The description never compensates, saying nothing about what limit bounds or how max_price_usd filters, so the agent must guess at two of three parameters.

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 resource and behavior: it routes one need to the best live x402 endpoints, ranked by on-chain payers then price, re-probed hourly. An agent can tell it discovers/ranks paid endpoints rather than running them. It does not, however, distinguish itself from siblings like route, find_resources, or search_all_catalogs.

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?

Gives clear context ('one question', 'free, no signup') and a detailed post-retrieval procedure: GET the url unpaid, read the 402 ask, pay in USDC on Base, retry. That is guidance on consuming results, not on when to choose this tool over the sibling search/route tools, and there are no exclusions.

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