Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_user

Retrieve the logged-in user's Rift Finance profile, including email, phone, display name, smart wallet address, and auto-swap settings. Requires authentication.

Instructions

Get the logged-in user's profile. Returns: email, phone, displayName, address (smart wallet), autoSwapEnabled, autoSwapTargetChain, and more. 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"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.6/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 disclosure burden. It does add value by naming concrete return fields (email, phone, displayName, address as smart wallet, autoSwapEnabled, autoSwapTargetChain) and by flagging the login requirement, but it says nothing about error behavior when unauthenticated, whether the data is cached, or pagination/partial responses for 'and more'.

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?

Three short sentences with the core purpose front-loaded, followed by return fields, then the prerequisite. The only soft waste is the trailing 'and more', which is vague but does honestly signal a truncated field list.

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 with no output schema, the description covers the essentials: what it returns, whose data it is, and the auth requirement. It could be more complete by noting what happens without a session, but nothing critical to invoking it correctly is missing.

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 of 4 applies; there is no parameter meaning that needs explaining. The description correctly implies no input is needed beyond being logged in.

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 states a specific verb and resource ('Get the logged-in user's profile'), which tells an agent this returns the current authenticated user rather than an arbitrary user record. It does not explicitly distinguish itself from close siblings such as rift_get_user_status or rift_get_user_tokens, so differentiation is only partial.

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?

The clause 'Requires login' establishes a prerequisite for calling the tool, which is real usage guidance. However, there is no statement of when to prefer this over rift_get_user_status or rift_get_user_tokens, and no exclusions or failure conditions are given, leaving selection between profile-level siblings to inference.

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