Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_onramp_status

Check the status of a crypto purchase with the transaction code returned by the buy request. Requires login.

Instructions

Check status of a crypto purchase. 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": {
      "transactionCode": "<transactionCode>"
    },
    "name": "rift_get_onramp_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
transactionCodeYesTransaction code from rift_buy_crypto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

C2.6/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. It does flag the login requirement, which is genuinely useful, but says nothing about whether this is a polling endpoint, what status states are returned, or whether repeated calls are safe.

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 action is front-loaded before the auth constraint. It is efficient, though the terseness borders on under-specification rather than true economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a status-checking tool with no output schema, the description should at least characterize the returned status semantics or lifecycle. With neither annotations nor an output schema, the agent is left guessing what a successful response contains.

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 description coverage is 100% and the single parameter is described as the transaction code from rift_buy_crypto, so the schema already does the work. The description adds no format or provenance detail beyond that, which is the baseline case.

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

Purpose3/5

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

"Check status of a crypto purchase" gives a verb and a resource domain, which is enough to know this is a lookup. However, it does not distinguish itself from near neighbors such as rift_get_onramp_orders or rift_poll_offramp_status, so an agent must guess which status tool applies.

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?

"Requires login" is a prerequisite, not usage guidance. The description never says when to call this versus listing onramp orders, nor that the transactionCode must come from rift_buy_crypto (that hint lives only in the schema).

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