Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_chains

Retrieve supported blockchain networks or details for a specific chain ID without authentication. Use it to identify available chains before bridging or sending crypto.

Instructions

Get supported chains or details for a specific chain. 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_chains"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainIdNoSpecific chain ID, or omit for all chains

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 burden; it does disclose 'No auth required', which is genuinely useful preconditions information, and 'Get' implies a read. It says nothing about error behavior for an invalid chainId, rate limits, or what 'details' actually contain, which are gaps for a tool with zero annotation coverage.

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?

Two short sentences with the dual behavior stated up front and the auth note trailing efficiently. Nothing is padded, though the second sentence is a bare precondition rather than integrated context.

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 simple one-optional-parameter read tool with no output schema, the definition gives enough to call it, but leaves what the returned chain details comprise and how an invalid ID is handled unspecified.

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 the single parameter's description ('Specific chain ID, or omit for all chains') already encodes the optionality. The description's 'or omit for all chains' restates the schema rather than adding format, example, or validation meaning.

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 uses a specific verb and resource ('Get supported chains') and covers both operating modes: a full list or details for a specific chain. It does not differentiate itself from the near-identical sibling rift_get_supported_chains, leaving real ambiguity about which to call.

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 only implied: passing a chainId yields details for that chain, omitting it returns all chains. There is no explicit when-not guidance and no named alternative, so the agent must infer the choice from the phrasing and schema default.

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