Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_wc_pair

Pair a DApp via WalletConnect by supplying a wc: URI and chain, enabling authenticated Rift Finance actions from AI chat.

Instructions

Pair with a DApp via WalletConnect. User provides a wc: URI (usually from a QR code). 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": {
      "uri": "<uri>",
      "chain": "<chain>"
    },
    "name": "rift_wc_pair"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYesWalletConnect URI starting with wc:
chainYesChain: BASE, ETHEREUM, POLYGON, ARBITRUM, CELO, etc

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the login/auth requirement and input provenance, but is silent on what pairing establishes (session persistence, topic, expiry) and what happens on an invalid or expired URI, which matters for a stateful connection tool.

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 with zero filler; the core action is front-loaded and the prerequisites follow. Every clause adds information an agent needs before calling.

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 two-parameter, no-output-schema tool, the definition covers the action, the input source, and the auth gate, which is the essential minimum. It falls short on post-call expectations — whether a session is now active and what the agent should do next — which an agent following a WalletConnect flow genuinely needs.

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%, so the schema already documents both uri and chain, establishing a baseline of 3. The description adds mild value by explaining the URI's origin ('usually from a QR code'), but says nothing about chain selection or accepted values beyond what the schema enumerates.

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: 'Pair with a DApp via WalletConnect', which is more precise than the bare name rift_wc_pair. It does not explicitly contrast with sibling flow tools like rift_wc_approve or rift_wc_sessions, so an agent must infer the position in the workflow, but the action itself is unambiguous.

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

Usage Guidelines3/5

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

The description gives a clear precondition ('Requires login') and implies when the tool applies (user has a wc: URI, typically from a QR code). However, it never states what to do after pairing or names the natural next step (e.g., approving a session request), leaving workflow guidance to inference from sibling names alone.

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