KeeSpecs

quote_bridge_route

Read-only

Whether a published one-hop bridge path exists between two chains for a token. Not a quote or a transfer. Returns the x402 payment quote for this read (price, network, asset, pay-to, and the exact URL). It does not return data. To buy, GET the returned URL over HTTP and pay with x402; check get_x402_health first.

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": {
      "from": "<from>",
      "to": "<to>",
      "token": "<token>"
    },
    "name": "quote_bridge_route"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Destination chain name
`from`	Yes	Start chain name
`token`	Yes	Ticker or token address

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.1/5.0

Behavior5/5

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

The description adds substantial behavioral context beyond the readOnlyHint and openWorldHint annotations: it returns an x402 payment quote rather than data, lists the quote fields, and explains the required HTTP GET plus x402 payment flow. This is exactly the kind of operational transparency needed for a paywalled read.

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 definition is front-loaded with the core purpose and then efficiently adds the key caveats and next step. 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.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description adequately explains what the tool returns (an x402 payment quote with price, network, asset, pay-to, and URL), what it does not return (data), and how to obtain the actual result. This is complete enough for an agent to invoke and act on the response correctly.

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% for the three simple parameters (from, to, token), so the schema already carries parameter meaning. The description reinforces the from/to/token concept but adds no format or semantic details beyond what the schema 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?

The description states a specific purpose: determining whether a published one-hop bridge path exists between two chains for a token, and clarifies that it is not a bridge quote or transfer. It is clear, but it does not explicitly differentiate from the similar sibling quote_bridge_speed beyond the general 'not a quote' caveat.

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?

Usage is mostly implied by the purpose. It names get_x402_health as a prerequisite and explains how to use the returned payment URL, but it does not state when to choose this tool over quote_bridge_speed or other quote_* siblings.

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

All KeeSpecs tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?