Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_set_api_url

Override the Rift Finance API base URL to connect to a custom deployment instead of the default endpoint.

Instructions

Override the Rift API URL. Only needed if using a custom deployment (not the default).

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": {
      "url": "<url>"
    },
    "name": "rift_set_api_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAPI base URL

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?

No annotations are provided, so the description carries the full behavioral burden. It discloses that this is an override with effect limited to custom deployments, which is useful context, but it does not state whether the change persists across sessions/processes, whether the URL is validated before being applied, or what happens on an invalid URL. For a global config mutation with zero annotation coverage, that leaves material gaps.

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, front-loaded with the action and immediately followed by the qualifying condition. No redundant restatement of the parameter or boilerplate.

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 config setter with a fully described schema and no output schema, the description covers what the tool does and when it is needed. Only persistence and validation behavior are missing, which is a minor gap at this complexity level.

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 single 'url' parameter is documented as 'API base URL', so the structured data already does the work. The description adds no format detail (scheme requirement, trailing slash handling, whether a path prefix is allowed), so baseline 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?

Names a specific verb+resource: 'Override the Rift API URL'. That distinguishes it from rift_set_api_key and rift_docs_url by the resource it targets (the base API URL, not credentials or docs). It stops short of explicitly contrasting with those siblings, so it is clear but not sibling-differentiating at the top level.

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 explicit when-to-use guidance: 'Only needed if using a custom deployment (not the default).' This tells an agent both the condition to call it and the default case where it is unnecessary. It omits practical context such as whether it must be called before other Rift tools, but the core routing guidance is present.

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