Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_send_payment_link

Deliver an existing payment link URL to a recipient via SMS or email. Use this to send a payment URL you already have; it does not create a payment.

Instructions

Send an existing payment link URL to someone via SMS and/or email. This does NOT create a payment — it just delivers an existing URL. You need to have a payment link URL already (e.g. from an invoice). At least one of recipientPhone or recipientEmail is required. 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": {
      "paymentLink": "<paymentLink>",
      "message": "<message>"
    },
    "name": "rift_send_payment_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesMessage to include with the link
paymentLinkYesThe payment URL to send
recipientEmailNoEmail to send to
recipientPhoneNoPhone number to send SMS to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.1/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 and does disclose useful traits: it is non-creating, requires login, and needs a pre-existing URL. It says nothing about delivery outcomes, failure modes when both recipient fields are empty, rate limits, or whether message content is validated/rendered verbatim, which leaves notable behavioral gaps for a tool that triggers outbound SMS/email.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the core action and appropriately short for a four-parameter tool. There is minor redundancy between "Send an existing payment link URL ... it just delivers an existing URL" and "You need to have a payment link URL already," which restates the same premise twice.

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 simple flat four-parameter tool with no output schema, the description covers purpose, prerequisite, channel requirement, and non-creating semantics. Remaining gaps (what happens if both recipient fields are omitted, delivery confirmation behavior) are minor but real.

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?

Schema coverage is 100%, so baseline is 3, but the description adds a constraint the schema does not encode: only paymentLink and message are required in the schema, yet the description establishes the cross-field rule that at least one recipient channel must be supplied. That is genuine semantic value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 ("Send an existing payment link URL") and immediately guards against the most likely confusion with a negative clause: "This does NOT create a payment — it just delivers an existing URL." An agent can tell this apart from link/invoice creation tools without inspecting the schema.

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

Usage Guidelines4/5

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

It states a concrete prerequisite ("You need to have a payment link URL already (e.g. from an invoice)") and a routing constraint ("At least one of recipientPhone or recipientEmail is required"). It does not name a specific alternative tool to obtain the URL, so guidance is strong but not fully explicit about the upstream step.

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