Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_wc_approve

Approve a pending DApp request and return a passkey approval link for the user to sign; then check the request status instead of retrying.

Instructions

Approve a pending DApp request. Always show the request details to user first. Returns an APPROVAL REQUIRED link: the user signs with their passkey there, then the DApp gets its answer. Check with rift_get_approval; 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": {
      "id": "<id>"
    },
    "name": "rift_wc_approve"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequest ID from rift_wc_get_requests

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses the out-of-band signing step ('user signs with their passkey there'), that the DApp receives the answer only after that, the login requirement, and warns against retry. It stops short of describing failure modes such as an expired or already-resolved request ID, which matters for a mutation-like approval flow.

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?

Four short sentences, front-loaded with the action, then prerequisites and the post-call path. Every sentence carries information; only the return-value sentence is slightly dense, packing link, signing, and DApp callback into one line.

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

Completeness4/5

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

For a one-parameter tool with no output schema, the description covers what an agent needs: the prerequisite user confirmation, the login requirement, that the return is an APPROVAL REQUIRED link rather than a completed approval, and the correct follow-up tool. Only error/expiry behavior is left unstated.

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% and the schema already explains that 'id' is the request ID from rift_wc_get_requests, so the baseline is 3. The description adds no additional meaning about the ID format, validity, or whether the ID must reference a still-pending request.

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?

The description uses a specific verb and resource ('Approve a pending DApp request') and distinguishes itself from the reject/disconnect siblings by naming rift_get_approval as the follow-up path. An agent can tell immediately what this tool does and what it is not for.

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?

Explicit guidance is given on preconditions ('Always show the request details to user first'), what to do afterwards ('Check with rift_get_approval'), and an explicit prohibition ('never call again to retry'), plus 'Requires login'. This is when-to-use, when-not-to-use, and the alternative in one short block.

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