Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_supported_chains

Retrieve supported blockchains with chain IDs, tokens, and fiat currencies plus payment methods so you can confirm which assets and networks Rift Finance supports.

Instructions

Get all supported blockchains (with chain IDs), tokens, and fiat currencies with payment methods.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.3/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 implies a read-only lookup and enumerates the categories of returned data, which is useful. However, it does not state whether the data is static reference data, whether it can be cached, or anything about the response shape or size.

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 front-loaded sentence with no filler, though the trailing 'fiat currencies with payment methods' is slightly ambiguous about whether payment methods attach to currencies.

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-parameter reference-data tool with no output schema, the description should sketch the structure of the response. It names the data categories but not their shape, nesting, or completeness, leaving the agent to discover the format on first call.

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 there is nothing for the description to disambiguate; the baseline of 4 applies. The mention of chain IDs and payment methods adds mild value about payload content rather than parameter 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?

States a specific verb and resource ('Get all supported blockchains ... tokens, and fiat currencies'), and the parenthetical '(with chain IDs)' clarifies the payload. It is clear what the tool returns, but it does not distinguish itself from siblings like rift_get_chains, rift_get_tokens, or rift_get_payment_methods, which appear to cover overlapping subsets.

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?

No when-to-use guidance is given at all. With siblings such as rift_get_chains and rift_get_tokens present, an agent cannot tell from the description whether this is the aggregate call to prefer or a redundant alternative.

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