Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_notifications_register

Registers a device for push notifications in Rift Finance by linking a unique subscriber ID and optional platform or device details.

Instructions

Register a device for push notifications. Requires login.

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": {
      "subscriberId": "<subscriberId>"
    },
    "name": "rift_notifications_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoweb or mobile
deviceInfoNoDevice description
subscriberIdYesUnique device/subscriber ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the login requirement, but says nothing about whether registration is idempotent, what happens if the device is already registered, or what the call returns.

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 waste, and the core action is front-loaded ahead of the auth prerequisite.

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?

The description covers purpose and authentication for a simple three-parameter tool with a fully documented schema and no output schema. It leaves gaps around duplicate-registration behavior and the outcome of the call, which matter for a mutation with no annotations.

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 description coverage is 100%, so subscriberId, platform, and deviceInfo are already documented in the schema. The description adds no meaning beyond that, so the baseline of 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?

The description gives a specific verb and resource: register a device for push notifications. It is clear what the tool does, but it does not distinguish itself from siblings such as rift_notifications_send or rift_notifications_subscriptions.

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?

"Requires login" establishes a prerequisite, and registering a device implies the usage context. However, there is no explicit guidance on when to use this instead of the subscriptions or send siblings, and no when-not conditions.

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