Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_bridge_routes

Retrieve available cross-chain bridge routes and supported tokens so you can plan crypto transfers between chains.

Instructions

Get available cross-chain bridge routes and supported tokens. No auth required.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose a genuinely useful trait — no authentication needed — which is real context an agent would otherwise have to discover by trial, and 'Get' implies a read-only, side-effect-free call. It stops short of saying whether the route list is live, cached, or static, and gives no rate-limit or freshness information.

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?

Two short sentences with no filler, and the core purpose is front-loaded before the auth note. Nothing is padded or repeated.

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?

For a zero-argument read tool with no annotations and no output schema, the description covers what the tool returns at a high level (routes and tokens) but gives no sense of the response shape, whether routes are per-chain-pair or global, or how to act on the result. An agent can call it correctly but cannot predict what comes back or what to do next.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to compensate for. The phrase 'supported tokens' does hint at the content of the response, but no argument semantics are required here.

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: 'Get available cross-chain bridge routes and supported tokens.' That is far better than the tautological sibling names like rift_get_chains, though it doesn't explicitly distinguish itself from rift_get_supported_chains or rift_get_tokens, which likely overlap on the 'supported tokens' half of the response.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of the natural next step (rift_bridge_quote or rift_bridge_execute), and no exclusion relative to the chain/token listing siblings that likely overlap. The only contextual cue is 'No auth required', which tells an agent it can call this freely but not why it should pick this tool over nearby discovery tools.

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

Deploy Server

Other Tools