Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_notifications_subscriptions

List or delete all notification subscriptions for your account. Requires login to manage notification preferences.

Instructions

Get or delete all notification subscriptions. Requires login.

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

Input Schema

NameRequiredDescriptionDefault
actionNo'get' to list, 'delete' to remove allget

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it does disclose the auth requirement and that deletion covers all subscriptions rather than one, which are the two most important behavioral facts. It omits irreversibility/confirmation behavior and what the get mode returns, leaving meaningful gaps for a bulk destructive operation.

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 operations and followed by the prerequisite. Nothing is repeated or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool with no output schema, the definition covers the essentials: operation choice, scope ('all'), and login requirement. It falls short of complete because a bulk delete with no annotations and no return-value documentation merits at least a note on irreversibility or delete confirmation.

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 enum values already carry descriptions ('get' to list, 'delete' to remove all), so the schema does the work. The description only restates that both modes apply to all subscriptions, adding no format or default detail 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 names the resource (all notification subscriptions) and the two supported operations (get, delete), so it is clear the tool both lists and bulk-removes subscriptions. It does not explicitly contrast itself with rift_notifications_register or rift_notifications_send, so sibling differentiation is left to the name and the 'all' scope.

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

Usage Guidelines2/5

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

'Requires login' is a useful prerequisite, and 'get or delete all' implies the two modes. However, there is no guidance on when to choose this over the register/send siblings, and no warning about the destructive nature of the delete mode (which removes ALL subscriptions, not one).

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