Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_transaction_history

Retrieve on-chain send and receive transaction history with chain and token filters. Requires login to access paginated results.

Instructions

Get on-chain transaction history (sends/receives). For offramp order history, use rift_get_offramp_orders. For onramp order history, use rift_get_onramp_orders. 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_transaction_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
chainNoFilter by chain
limitNoNumber of transactions (default 10)
tokenNoFilter by token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.8/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 behavioral burden. It usefully discloses that results are on-chain only (excluding onramp/offramp order records) and that login is required, but says nothing about ordering, pagination behavior, or how page/limit interact.

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, front-loaded with the core purpose before the sibling routing and the auth requirement. Every sentence carries information; only the auth note is mildly tacked on.

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?

Covers purpose, scope boundaries, auth, and parameter documentation via the schema, and no output schema means return values needn't be explained. However, for a paginated history endpoint with no annotations, the absence of any pagination or ordering guidance leaves a real gap.

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%, with all four optional parameters documented inline including the default limit of 10. The description adds no meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource (on-chain transaction history) and immediately narrows scope to sends/receives, which separates it from the order-history siblings. An agent can tell what it returns 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?

Explicitly routes the agent to rift_get_offramp_orders and rift_get_onramp_orders for those order histories, so the main disambiguation is stated rather than inferred. It stops short of covering other adjacent siblings such as rift_get_deposits or rift_get_transaction_fee, so no exclusion for those cases.

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