Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_search_docs

Search Rift Finance SDK and API documentation to find method signatures, code examples, and authentication requirements for sending crypto, offramping, or bridging.

Instructions

Search Rift Finance SDK/API documentation. Returns method signatures, code examples, and auth requirements.

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": {
      "query": "<query>"
    },
    "name": "rift_search_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat you want to look up (e.g. 'send USDC', 'offramp', 'bridge quote')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.6/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 helpfully discloses the shape of returned content (method signatures, code examples, auth requirements), but says nothing about whether results are semantic or keyword matches, how many are returned, or whether there are rate limits.

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?

Two short sentences with no filler; the purpose is front-loaded and the return-value hint follows immediately. Nothing is wasted.

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 documentation lookup with no output schema and no annotations, the description covers purpose and return content adequately. A note on search behavior or result limits would close the remaining gap.

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?

There is a single required parameter with 100% schema description coverage, including concrete examples ('send USDC', 'offramp', 'bridge quote'). The prose only restates the domain of the query rather than adding format or scoping guidance beyond the schema, so the baseline of 3 applies.

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 concrete verb and resource ('Search Rift Finance SDK/API documentation') and adds what kind of results come back (method signatures, code examples, auth requirements). It does not name or contrast with the closest sibling, rift_docs_url, so the agent must infer the difference.

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?

Usage is implied: look up SDK/API documentation by query. There is no explicit statement of when to prefer this over rift_docs_url or rift_get_api_endpoints, and no exclusions or prerequisites are given.

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