Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_sign_message

Sign a message with the user's Safe smart wallet for DApp authentication or off-chain signatures; returns an approval link the user confirms with a passkey.

Instructions

Sign a message with the user's Safe smart wallet (ERC-1271 contract signature; ERC-6492-wrapped if the wallet isn't deployed on that chain yet). Used for DApp authentication, off-chain signatures, etc. Returns an APPROVAL REQUIRED link the user approves with their passkey; the signature is in rift_get_approval's result. Never call again to retry. 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": {
      "chain": "<chain>",
      "message": "<message>"
    },
    "name": "rift_sign_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesChain to use for signing
messageYesMessage to sign

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the behavioral load and does so thoroughly: it describes the async 'APPROVAL REQUIRED' link, passkey approval, retrieval of the signature via rift_get_approval, the no-retry rule, and the login requirement. It also clarifies the ERC-1271/ERC-6492 signing behavior, giving an agent enough to understand the flow.

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?

The description is compact and front-loaded: it states the action first, then usage, return flow, and operational constraints. Every sentence provides useful information, with only the word 'etc.' being mildly loose.

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?

No output schema or annotations exist, so the description must carry purpose, return path, and operational constraints; it does. It explains the approval-link return, deferral to rift_get_approval for the signature, login requirement, and no-retry warning. Missing rejection or expiration details are minor for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema baseline is 3. The description adds meaning for the chain parameter by explaining that signing uses ERC-6492 wrapping if the wallet is not deployed on that chain, and frames the message as an ERC-1271 contract signature. Message encoding is not explained, but the description adds useful semantics beyond the schema.

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: 'Sign a message with the user's Safe smart wallet', and adds standards context (ERC-1271 contract signature; ERC-6492 wrapping when the wallet is undeployed). It does not explicitly distinguish this from sibling rift_sign_transaction, so it stops short of the top score.

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?

It supplies usage contexts ('DApp authentication, off-chain signatures') and a clear prohibition ('Never call again to retry'), plus a prerequisite ('Requires login'). It lacks an explicit alternative-tool routing statement, such as when to use rift_sign_transaction instead.

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