Skip to main content
Glama

Agent Exchange router

Route me to the right paid API

route
Read-only

Say what you need in plain words (e.g. "bitcoin price", "web search", "screenshot a URL"). Returns the one paid API that buyers actually pay for (distinct buyers in 30 days) and that answered a valid x402 402 to our check seconds ago, the exact request to send, and that seller's payment terms so you can pay on your first request; up to four alternatives. Free, no key. Same as GET https://bazaar.agentexchange.work/route.json?need=

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": "route"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYeswhat you need, in plain words
networkNooptional: base | solana | polygon | ...
max_price_usdNooptional: only routes at or below this price

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Goes well past the readOnlyHint/openWorldHint annotations by explaining the selection criteria: sellers with distinct paying buyers in the last 30 days plus a live x402 402 challenge validated seconds ago. That is meaningful, non-obvious behavioral context, and 'free, no key' removes an auth question. It stops short of saying what happens when nothing matches or how stale a cached answer can be.

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 dense sentence plus a short equivalence clause; the input instruction and the payoff are front-loaded, so an agent learns how to call it and what it gets within the first clause. Some sub-clauses (distinct buyers in 30 days, the 402 re-check) crowd together and could be split for scannability.

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, the description carries the return-value burden and does name the main fields (chosen API, exact request, payment terms, up to four alternatives). It omits the shape of the response, how alternatives are ordered, and the no-match behavior — gaps an agent calling it blind would care about.

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 description coverage is 100%, so the schema already defines all three parameters and the baseline is 3. The plain-language examples ('bitcoin price', 'web search', 'screenshot a URL') add modest intuition about the expected granularity of need, but network and max_price_usd are never elaborated beyond their schema text.

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 act (routing a plain-language need to a paid API) and describes precisely what comes back: the chosen API, the exact request to send, and the seller's payment terms. It is clearly distinct in kind from siblings like ask or search_all_catalogs, though it never names them to sharpen the contrast.

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?

Implies the trigger well — describe your need in plain words, with three concrete examples — and discloses that it is free and needs no key, which lowers the cost of trying it. But it offers no when-not guidance and never distinguishes itself from sibling discovery tools such as find_resources or search_all_catalogs, leaving the agent to infer which catalog lookup to reach for.

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