Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_tokens

Retrieve supported token types with metadata—name, contract address, and chain—filtered by chain ID. Use it to discover tokens, not to check balances.

Instructions

Get the list of supported token TYPES (metadata: name, contract address, chain). This is NOT balances — use rift_get_balance for balances. 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_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainIdNoChain ID to filter (e.g. '8453' for Base, '137' for Polygon)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden; it usefully states "No auth required" and its read-only nature is implied by "Get." It does not say whether results are paginated, whether the list is static/cacheable, or the shape of the response beyond the three named metadata fields, so gaps remain for a zero-annotation tool.

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?

Three short sentences, each doing distinct work: what it returns, what it is not, and the auth requirement. The disambiguation is front-loaded immediately after the capability statement with no filler.

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 one-optional-parameter, read-only lookup with no output schema and no annotations, the description covers the essential qualifiers: returned fields, auth, and the nearest sibling confusion. The only meaningful omission is default behavior when chainId is absent.

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 optional chainId already documents the filter with examples ('8453' for Base, '137' for Polygon). The description adds no filter-specific meaning, notably not stating what happens when chainId is omitted (presumably all chains), so baseline 3 is correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Get the list of supported token TYPES") and pins down the payload (metadata: name, contract address, chain). It goes further and explicitly contrasts the resource with balances, so an agent can distinguish it from the sibling it is most likely to be confused with.

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

Usage Guidelines4/5

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

Names the alternative and the condition that selects it: "This is NOT balances — use rift_get_balance for balances." That covers the highest-risk misroute, but it does not address ambiguity against rift_get_user_tokens or rift_get_supported_chains, so an agent must still infer those boundaries.

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