Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_logout

Ends your Rift Finance session and clears stored authentication, so you must log in again before using any authenticated tools.

Instructions

Logout and clear the session. After this, user must login again to use authenticated tools.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses the destructive effect (session cleared) and the concrete consequence (the user must log in again, and authenticated tools will stop working). It stops short of stating whether server-side tokens are revoked, what happens if no session exists, or what the response looks like.

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 zero filler, action first and consequence second. The front-loaded verb makes the tool's identity obvious at a glance.

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, non-annotated session-termination tool, the description covers what matters: the action and its authentication consequence. The only omissions are return-value shape and behavior when no session exists, both minor 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 there is no parameter semantics to explain and the baseline applies. The description correctly avoids inventing options and simply describes the effect of the call.

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 gives a specific verb ('Logout') plus the side effect ('clear the session'), so the agent knows exactly what the tool does. It doesn't need to distinguish itself from a named alternative, since no sibling offers an equivalent session-ending action, but it also makes no explicit differentiation from state-mutating siblings like rift_delete_user.

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 only implied: the agent must infer that this should be called when the user wants to end their session. There is no explicit when-to-use, when-not-to-use, or warning about calling it mid-task, and no mention of related siblings such as rift_get_user_status to check session state first.

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