Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_onramp_orders

Fetch onramp purchase history for a specified user ID; login is required. Review past crypto buy orders and verify onramp transactions.

Instructions

Get onramp purchase history. Requires login.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "userId": "<userId>"
    },
    "name": "rift_get_onramp_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesUser ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. The login requirement is a genuine behavioral trait, but nothing is said about the shape of the returned history, pagination, whether the userId must match the authenticated user, or what happens when no purchases exist.

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 no filler, and the purpose is front-loaded ahead of the prerequisite. Brevity is appropriate, though the second sentence could carry more weight than just the auth note.

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 single-parameter read tool with no output schema, the definition covers what the tool returns at a conceptual level (purchase history) and the auth prerequisite. It is still silent on result format and the identity relationship between userId and the logged-in session, which an agent would need to call it reliably.

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 there is only one parameter, userId, which the schema already documents as "User ID". The description adds no meaning about whose ID is acceptable or whether it must match the logged-in user, so the baseline 3 applies.

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 names a specific verb and resource ("Get onramp purchase history"), which cleanly separates it from the offramp counterpart sibling rift_get_offramp_orders. It stops short of explicitly contrasting with any sibling, but the onramp/offramp distinction in the resource name does the work.

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?

"Requires login" supplies one concrete precondition for invoking the tool, which is useful context. There is no explicit guidance on when to choose this over rift_get_offramp_orders or rift_get_transaction_history, so routing must be inferred from the resource name.

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