Skip to main content
Glama

get_recurring_invoice_history

Read-onlyIdempotent

Read the subscription status and billing history for a recurring invoice in the approved business. Amounts are in minor units and timestamps are Unix seconds. Use nextCursor for more history. Share reviewUrl with the owner to review an unpaid renewal and retry it in Sales.

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": {
      "id": "<id>"
    },
    "name": "get_recurring_invoice_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior. The description adds material context beyond them: minor-unit amounts, Unix-second timestamps, cursor pagination, and a reviewUrl workflow for unpaid renewals. It does not cover auth or rate limits, but it is substantially informative.

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: purpose, data conventions, pagination, and follow-up action. The information is front-loaded and no sentence is filler; the only blemish is the 'nextCursor' naming mismatch, not verbosity.

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 two-parameter read tool with no output schema, the description supplies useful return-side conventions (minor units, Unix seconds) and next-step behavior (reviewUrl). It leaves the required id and the shape of the history response underspecified, so it is not fully complete.

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 coverage is 0% for two parameters, so the description must carry the semantics. It never explains the required id beyond 'recurring invoice,' and it refers to 'nextCursor' while the schema parameter is named 'cursor,' which can mislead an agent wiring the call.

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 read operation and resource: subscription status plus billing history for a recurring invoice, limited to an approved business. It is clearly a read-history tool and not the sibling setter, though it does not name the alternative 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?

It gives operational guidance for pagination and for using reviewUrl after an unpaid renewal, but it does not explicitly say when to choose this over sibling read tools or set_recurring_invoice_renewal. Usage is implied rather than contrasted.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources