Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_poll_offramp_status

Check the status of an offramp order after initiating a transfer, confirming whether it is pending, completed, or failed. Requires login.

Instructions

Check the status of an offramp order. Call after rift_offramp. Status: PENDING → COMPLETED or FAILED. 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>",
      "currency": "<currency>"
    },
    "name": "rift_poll_offramp_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyYesCurrency of the order
transactionCodeYesTransaction code from the offramp order

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden, and it does add real context: it requires login and reports the terminal states a check can return. What it omits is whether the call is read-only, whether polling is rate-limited or should be spaced, and whether a failed order carries an error reason.

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?

Four short statements, front-loaded with the action, then the sequence, then the state machine, then the auth caveat. Nothing is padded, and the arrow notation conveys the lifecycle more compactly than prose would.

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 two-parameter tool with no output schema, an agent cannot tell what fields the status response contains beyond the status code, for example an error reason or amount. The auth and lifecycle notes cover the process, but the return payload is left undescribed.

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%, so transactionCode and currency are already described in the schema, and the description adds nothing about their format, source, or valid values. By the baseline rule, a 3 is the correct ceiling when the schema already does the work.

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 gives a specific verb and resource: 'Check the status of an offramp order', which reads clearly as a single-order status lookup. It falls short of a 5 because it does not distinguish itself from rift_get_offramp_orders, the list variant a sibling catalog suggests exists.

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?

'Call after rift_offramp' gives an explicit sequencing rule that tells the agent exactly when this tool is appropriate, and the PENDING → COMPLETED or FAILED chain implies when polling should stop. There is no explicit statement of when not to use it, and the list-versus-single-order distinction from rift_get_offramp_orders is left implicit.

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