Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_notifications_send

Sends a push notification to all of a logged-in user's registered devices, including an optional title and tap-through URL.

Instructions

Send a push notification to all of the user's registered devices. 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": {
      "message": "<message>"
    },
    "name": "rift_notifications_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoNotification title
messageYesNotification body
targetUrlNoURL to open when tapped

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose two valuable behavioral facts: delivery goes to ALL registered devices (non-targeted fan-out) and login is required. It omits rate limits, whether the send is idempotent or retryable, and what happens on partial delivery failure.

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, zero filler, with the scope stated before the auth requirement. Nothing could be removed without losing information.

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 low-complexity, three-parameter send tool with fully documented schema and no output schema, the description covers enough to call it correctly. The only meaningful gap is that no return/response behavior is described, which matters slightly since no output schema exists to compensate.

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 every parameter already has a description (title, message, targetUrl), so the schema does the semantic work. The description adds no format hints, length limits, or constraints for the message body or URL beyond what is structured.

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?

States a specific verb and resource ("Send a push notification") plus the fan-out scope ("all of the user's registered devices"). An agent can distinguish this from registration/subscription siblings by the word "Send", though the description never explicitly contrasts with them.

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 implied by the broadcast wording and the "Requires login" prerequisite, which tells the agent auth is mandatory before calling. There is no explicit when-not guidance or named alternative for targeted versus bulk delivery.

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