Skip to main content
Glama

get_routes

Read-only

List supported swap routes (source/destination chain and token pairs).

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

Input Schema

NameRequiredDescriptionDefault
dst_chainNoOnly routes to this chain, e.g. "ethereum"
src_chainNoOnly routes from this chain, e.g. "bitcoin"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-data profile is known. The description confirms this is a supported-route catalog (static discovery data), which is mild added context, but says nothing about result shape, ordering, or whether the route set is dynamic or cached.

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?

A single well-formed sentence with the key concept front-loaded and zero filler. It is tight, though it leaves room for a short clause about filtering by chain that would have cost nothing.

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 two-optional-parameter read-only listing tool with fully documented schema and no output schema, the definition supplies enough to call it correctly. Only the return content and filtering behavior remain unstated, which is a minor gap at this complexity.

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 coverage is 100% and both filters carry descriptions with examples, so the schema does the heavy lifting. The description's mention of source/destination chain and token pairs hints that filtering is possible but adds no syntax or matching semantics beyond what the schema already provides.

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 verb and resource ('List supported swap routes') and clarifies the scope as source/destination chain and token pairs, so an agent knows this is a discovery read, not a quote. It does not explicitly distinguish itself from get_quote or get_max_spendable, but the read-only enumeration purpose is unambiguous.

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?

The intent to enumerate available routes is implied, and the schema's filter parameters suggest narrowing by chain, but the description never says when to prefer this over get_quote or quote_and_create, nor any prerequisites. Usage is inferable rather than stated.

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