Skip to main content
Glama

Client statement

get_client_statement
Read-onlyIdempotent

Use this when the user asks for a client's statement of account, a client's invoices and payments over a period, or what a client owes with a running balance. A client's statement for a period, as in the statement in Fatura Go: their issued invoices dated in the period with payments, credit notes and write-offs, a running balance, and totals per currency (invoiced, paid, written off, outstanding, unused credit). brought_forward is separate: what is still unpaid today on earlier invoices (the statement itself starts at 0). Default period: 1 January this year to today. At most the last 100 lines per currency. app_url opens the client, where the user downloads or emails the statement. Do not use it for one invoice (get_invoice) or for all clients' balances (list_clients).

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": {
      "client_id": "<client_id>"
    },
    "name": "get_client_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_toNoYYYY-MM-DD, document date on or before.
client_idYesFrom list_clients.
date_fromNoYYYY-MM-DD, document date on or after.
business_idNoFrom list_businesses. May be left out when the connection shares exactly one business.
unpaid_onlyNoOnly invoices with something left to pay.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds real behavioral context beyond that: the default period (1 January this year to today), a hard cap of the last 100 lines per currency, the semantics of brought_forward as separate from the statement, and that app_url is where the user downloads or emails the statement. Not quite a 5 because it doesn't say what happens when a client has more than 100 lines (truncation vs. paging signal) or whether the statement is generated live vs. cached.

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?

Information-dense and front-loaded: trigger phrases first, then output contents, then defaults and limits, then routing exclusions last. Loses a point for awkward construction — the mid-paragraph fragment 'A client's statement for a period, as in the statement in Fatura Go:' and the bare 'brought_forward is separate' sentence break the flow without adding much.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must describe the return, and it does: per-currency line items, running balance, and the five totals (invoiced, paid, written off, outstanding, unused credit), plus the 100-line cap and the app_url destination. For a read-only report tool with fully documented parameters, nothing an agent needs in order to call it or interpret the result is missing.

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 the baseline is 3, but the description adds meaning the schema lacks: the default period for date_from/date_to, and the framing that unpaid_only relates to invoices with something left to pay while brought_forward reflects unpaid earlier invoices. It does not explicitly explain business_id's single-business fallback, which the schema already carries, so this is a 4 rather than a 5.

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?

States a specific verb+resource ('client's statement of account') and then enumerates exactly what the output contains: issued invoices dated in the period, payments, credit notes, write-offs, a running balance, and totals per currency. It explicitly separates itself from get_invoice (single invoice) and list_clients (all clients' balances), so an agent can route correctly without opening 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 Guidelines5/5

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

Opens with the triggering user intents ('a client's statement of account', 'invoices and payments over a period', 'what a client owes with a running balance') and closes with explicit exclusions naming the alternatives (get_invoice, list_clients). Both when-to-use and when-not-to-use are covered.

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