Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_invoices

List invoices by status and date range with sort order to review payment status and billing activity. Login required.

Instructions

List invoices. Filter by status, date range, and sort order. 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_get_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortByNocreatedAt, updatedAt, or paidAt
statusNoPENDING, COMPLETED, or EXPIRED
sortOrderNoasc or desc

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and only partially meets it. It discloses the login requirement, but says nothing about pagination, result limits, default sort order, or whether it returns only the caller's invoices or all invoices — critical for a listing endpoint.

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?

Three short, front-loaded sentences with no filler. The only defect is that one of them references a capability the schema does not support, which is wasted (and misleading) space rather than verbosity.

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?

With no output schema and no annotations, the agent has no structured fallback for return shape or pagination behavior, and the description does not supply it. It is minimally adequate for a simple three-optional-parameter list tool, but leaves meaningful gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the three parameters are already documented, and the description adds no syntax detail for them. Worse, it advertises a 'date range' filter that does not exist in the input schema, which could lead an agent to pass a bogus parameter or expect unsupported behavior.

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 leads with a specific verb and resource ('List invoices') and enumerates the filtering dimensions, so an agent immediately knows this is a read/list operation. It is distinguishable from the obvious mutation sibling rift_create_invoice by the verb alone, though no sibling is named.

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' is a real usage prerequisite that tells the agent authentication is needed before calling. Beyond that there is no when-to-use versus alternative guidance (e.g., when to use this instead of rift_get_transaction_history for financial records).

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