Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_docs_url

Returns the public Rift Finance docs portal URL so you can point developers to integration walkthroughs for client-side, server SDK, HTTP API, and transaction signing without dashboard login.

Instructions

Return the URL of the public Rift docs portal. Use this to point a developer at integration walkthroughs (client-side, server SDK, HTTP API, transaction signing) without requiring them to log in to the dashboard.

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_docs_url"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden, and it does disclose the key traits: the portal is public and requires no authentication, and it enumerates the covered topic areas. It does not say whether the URL is static or environment-dependent (relevant given the rift_set_api_url sibling), which is the main residual gap.

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 sentences, front-loaded with the return value, then the usage rationale. No repetition of the tool name and no filler; every clause adds either purpose or context.

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 zero-parameter getter with no output schema, the description covers what is returned (a URL) and why it matters (public, no login). Only the static-vs-configurable nature of the URL is left unstated, a minor omission for a tool this simple.

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 the baseline is 4; there is nothing for the description to disambiguate. It correctly implies the call is argument-free by framing the result as a single fixed portal URL.

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: 'Return the URL of the public Rift docs portal.' That is unmistakably a URL getter rather than a content search, which implicitly separates it from rift_search_docs, but it never names or contrasts the sibling explicitly, so an agent must infer the split.

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?

Gives a clear use case: point a developer at integration walkthroughs (client-side, server SDK, HTTP API, transaction signing) without dashboard login. The condition is concrete and actionable, though there is no explicit 'do not use this when...' clause or named alternative for retrieving doc content.

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