Skip to main content
Glama

Get invoice totals

crunch_get_invoice_totals
Read-only

Retrieve sales invoice totals with optional filters for client, status, issue or due dates, invoice number, or recurring invoices. Returns the amount invoiced, owed to you, and owed by you.

Instructions

Get sales invoice totals: with no filters, everything invoiced and still outstanding; with filters (client, status, issue or due dates, invoice number, recurring), the amount invoiced, owed to you and owed by you for the matching invoices.

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": "crunch_get_invoice_totals"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoOnly invoices with this status, as Crunch names it
client_idNoOnly this client's invoices
recurringNoOnly recurring (true) or one-off (false) invoices
due_to_dateNoDue on or before (YYYY-MM-DD)
due_from_dateNoDue on or after (YYYY-MM-DD)
invoice_numberNoOnly this invoice number
issued_to_dateNoIssued on or before (YYYY-MM-DD)
issued_from_dateNoIssued on or after (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description's job is to add return semantics — and it does, naming the three figures returned (amount invoiced, owed to you, owed by you), which is valuable since there is no output schema. It does not address currency handling, tax treatment, or how the aggregates are computed.

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?

A single well-structured sentence that front-loads the unfiltered case before the filtered case, with no filler. It is dense but readable; a slightly tighter phrasing could trim the parenthetical filter list that the schema already covers.

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 an eight-parameter, zero-required aggregation tool with no output schema, the description supplies the one thing the schema cannot: what the returned totals mean. Remaining gaps (currency, tax basis, whether zero-result filters return nulls) are minor but real.

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%, so all eight filters are already documented with patterns and semantics. The description groups them ('client, status, issue or due dates, invoice number, recurring') and frames them as conjoint filters, but adds no syntax or precedence detail beyond the schema. 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?

States a specific verb and resource ('Get sales invoice totals') and specifies the scope both with and without filters, which distinguishes it from a single-invoice read like crunch_get_invoice. It never names a sibling tool or explicitly contrasts with one, so it falls short of a 5.

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 explains the two usage modes (no filters = all invoiced and outstanding; with filters = totals for matching invoices), which implies when each is appropriate. It gives no explicit when-not guidance and does not point to alternatives such as aged debtors/creditors or the single-invoice tool for per-invoice detail.

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