Skip to main content
Glama

Agent Exchange store

get_route_api

Which paid API should I call? Give a task in plain words and get the best live x402 endpoint for it plus up to four alternatives: URL, method, price, network, seller and the exact request, each re-checked for liveness. Call it before buying from an unknown seller. A need with no match is not charged.

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

Input Schema

NameRequiredDescriptionDefault
x_paymentNoSigned x402 payment payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that results are re-checked for liveness and that unmatched needs are not charged, but it does not explain the payment/authorization mechanics of x_payment or clarify whether a matched request incurs a charge.

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?

The description is concise and front-loaded, starting with the core routing question and then stating the result and its fields. Every sentence contributes useful information with no 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 discovery tool with no output schema, the description gives a strong picture of the returned endpoint data, alternatives, and liveness checks. It is slightly incomplete because it never ties x_payment to payment or authorization behavior, but the core usage scenario is well covered.

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 single parameter is documented in the schema. The description does not mention x_payment at all and therefore adds no meaning beyond the schema for the parameter.

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?

The description gives a specific verb and resource: submit a task in plain words and receive the best live x402 endpoint plus alternatives. It clearly frames the tool as a discovery/routing helper, but does not explicitly distinguish it from similarly named siblings such as route or get_recommend.

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

Usage Guidelines4/5

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

It gives a clear usage trigger: call before buying from an unknown seller. It also clarifies that a need with no match is not charged, which helps the agent decide to call it. It lacks explicit when-not-to-use guidance or named alternatives.

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