Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_user_tokens

Retrieve the list of token types a user has interacted with on Rift Finance, excluding balances. Use this metadata to identify relevant tokens, then check actual balances separately.

Instructions

Get the list of token TYPES the user has interacted with (metadata, not balances). For actual balances, use rift_get_balance. Requires login.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.2/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 burden; it does disclose two useful traits — this is a metadata read, not a balance read, and it requires authentication. It says nothing about pagination, ordering, whether an empty list is possible, or whether the result spans chains/testnets, which are real behavioral questions for a list endpoint.

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, front-loaded with the primary purpose and immediately followed by the disambiguation and prerequisite. Every clause earns its place; nothing is padding.

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 zero-parameter read tool with no output schema, the description covers the essentials: what it returns conceptually, what it does not return, and the auth requirement. The main remaining gap is not describing the shape of each token entry (fields per type), which an agent would need before composing downstream calls.

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; there are no parameter semantics to disambiguate. The description correctly implies the user scope is fixed rather than passed in.

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?

"Get the list of token TYPES the user has interacted with" names a specific verb and resource, and the parenthetical "(metadata, not balances)" preempts the most likely misreading. It explicitly contrasts with rift_get_balance, so an agent can pick correctly without opening the schema.

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?

It gives a clear selection rule: use this for token type metadata, use rift_get_balance for actual balances. The "Requires login" clause flags a precondition. It stops short of stating when-not to call (e.g., no login, or non-user-scoped queries), so it falls just short of a 5.

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