Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_wc_get_requests

Fetch pending transaction requests from connected DApps so users can review and approve them; login is required.

Instructions

Get pending transaction requests from connected DApps. Show these to the user for approval. 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_wc_get_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations supplied, the description must carry the full behavioral burden. It usefully discloses the auth prerequisite and that results are meant for user review, but says nothing about whether the request queue is consumed, whether the call blocks or polls, or how pending requests relate to rift_wc_sessions.

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 resource and scope, then the required agent behavior, then the prerequisite. Nothing is redundant or padded.

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 no-param, no-output-schema, no-annotation tool, the description covers purpose, the user-approval step, and login requirement. It omits the shape of a returned request (chain, transaction payload) and whether approving is the next mandatory step, leaving the agent to discover the queue's lifecycle by trial.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; the baseline applies. The description correctly signals a parameterless call, so the agent knows no filtering arguments are available.

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?

States a specific verb and resource with scope: 'pending transaction requests from connected DApps.' That cleanly separates it from siblings like rift_wc_sessions (session listing) and rift_wc_approve (acting on a request), though no sibling is named explicitly.

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?

Adds a workflow directive -- 'Show these to the user for approval' -- which tells the agent this is a human-in-the-loop read, plus the prerequisite 'Requires login.' It stops short of naming the follow-up tools (rift_wc_approve / rift_wc_reject) or saying what to do when the list is empty.

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