Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_set_api_key

Configure the Rift API key (sk_...) to authenticate and enable live Rift Finance actions; call this before other live tools when no key is set.

Instructions

Set the Rift project API key. MUST be called before any other live tool if no key is configured. The key starts with 'sk_'. Ask the user for it if you don't have it.

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": {
      "apiKey": "<apiKey>"
    },
    "name": "rift_set_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyYesRift API key starting with sk_

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden and does disclose the key format and the bootstrap prerequisite. It does not say whether the key is persisted across sessions, whether setting it overwrites an existing key, what happens on an invalid key, or any handling caution for a secret value.

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, each doing distinct work: the operation, the ordering prerequisite, and the missing-input fallback. The critical prerequisite is front-loaded and there is no filler.

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 configuration setter with no output schema, the essential information needed to call it correctly is present, including the ordering constraint relative to other live tools. Only secondary details such as overwrite behavior and validation failure modes are absent.

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 apiKey parameter is already described as starting with 'sk_', which the description merely repeats. The added value is the instruction to source the key from the user rather than fabricate one, which goes slightly beyond the schema.

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?

The description states a specific verb and resource ('Set the Rift project API key'), making the operation unambiguous. It does not explicitly contrast itself with the nearby rift_set_api_url sibling, so the differentiation is inferred from the resource noun rather than stated.

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

Usage Guidelines5/5

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

It gives an explicit precondition ('MUST be called before any other live tool if no key is configured') and an explicit fallback behavior ('Ask the user for it if you don't have it'). The agent knows exactly when to invoke this and what to do when the key is absent.

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