Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_sign_transaction

Indicates that raw EOA transaction signing has been removed, returning a 410 error so older prompts fail clearly; use rift_send_transaction to execute through a Safe instead.

Instructions

REMOVED: raw EOA transaction signing. Rift wallets are passkey-owned Safe smart accounts with no EOA key, so the server answers 410 EOA_SIGNING_REMOVED. Use rift_send_transaction (executes through the Safe, returns an approval link) instead. Kept only so old prompts get a clear error.

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": {
      "chain": "<chain>"
    },
    "name": "rift_sign_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoContract/recipient address
dataNoEncoded contract call data (hex)
chainYesChain
valueNoValue in wei

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses the exact status code and error identifier (410 EOA_SEND... EOA_SIGNING_ERROR) an agent will encounter, plus the architectural reason (passkey-owned smart account, no private key). It also discloses a behavioral trait of the replacement (returns an approval link), which is the kind of detail an agent needs to sequence calls.

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?

Three short sentences, front-loaded with the removal status and the error code, then the redirect, then the rationale for retention. No filler, and the most decision-critical fact (it does not work) is first.

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

Completeness5/5

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

For a deliberately non-functional 4-parameter tool with no annotations and no output schema, the description supplies everything an agent needs: it is dead, here is the exact error, here is the tool to call instead and what that tool returns. Nothing required to call it correctly is missing.

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%, so the schema already explains to/data/chain/value and the baseline of 3 applies. The description adds nothing parameter-specific, and notably does not say whether the supplied parameters are ignored or validated before the 410 is returned — a small missed opportunity, but not a real ambiguity given the tool always fails.

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?

"REMOVED: raw EOA signing" immediately states what the tool used to do and that it is no longer functional, and the description goes on to give the concrete failure mode (HTTP 410 EOA_SIGNING_REMOVED). An agent can tell within one line that this is a tombstone, not an actionable signer, and distinguish it from rift_send_transaction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the replacement explicitly ("Use rift_send_transaction (executes through the Safe, returns an approval link) instead") and describes why, plus the reason the tool still exists ("Kept only so old prompts get a clear error"). When-to-use, when-not-to-use, and the alternative are all spelled out with no inference required.

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