Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_create_invoice

Create a crypto payment invoice and generate a shareable payment URL for recipients on supported chains; include description, token, and amount. Requires login; KYC applies above $20.

Instructions

Create a payment invoice and get a payment URL. No OTP required. KYC required for >$20. 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": {
      "description": "<description>",
      "chain": "<chain>",
      "token": "<token>",
      "amount": "<amount>"
    },
    "name": "rift_create_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesChain: BASE, POLYGON, ARBITRUM, ETHEREUM, CELO, etc
tokenYesToken: USDC, USDT
amountYesAmount to invoice
descriptionYesInvoice description (shown to payer)
recipientEmailNoCustomer's email — sends invoice link
recipientPhoneNoCustomer's phone — sends invoice link via SMS

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description does real work: it discloses the auth requirement, the OTP-free path, the $20 KYC threshold, and that the caller receives a payment URL. Not covered is what happens when the KYC gate fails or whether the returned URL expires, but the mutation's key behavioral traits are surfaced.

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?

Four short sentences, front-loaded with purpose and outcome, then the operational constraints. No restated name, no filler, and each sentence carries a distinct fact an agent needs.

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 six-parameter mutation with no annotations and no output schema, the description covers purpose, return value, auth, and the KYC gate. Only edge behavior (KYC failure handling, invoice link lifecycle) is absent, which is a modest gap for this complexity.

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%, with each of the six parameters already documented including enum-like chain/token examples and the email/SMS notification effect of recipient fields. The description adds no parameter-level meaning beyond that, so the baseline 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?

A specific verb-plus-resource statement ('Create a payment invoice') plus the outcome ('get a payment URL'), which tells an agent exactly what calling it produces. It is distinguishable from read-side siblings such as rift_get_invoices by the create verb, though no alternative is named explicitly.

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?

The description supplies usable preconditions ('Requires login', 'KYC required for >$20', 'No OTP required') that imply when the call will succeed. It does not, however, say when to prefer this over related flows like rift_offramp_create_order or rift_create_recovery, leaving the choice to inference.

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