Skip to main content
Glama
Sign In

YESbusiness

by ch.yesbusiness
OverviewDiscussionsAdmin

Account statement

get_account_statement
Read-onlyIdempotent

The account statement: the movements of one or more accounts over a date range, as a flat list of ledger rows with a running balance — this is the tool for 'what happened on account X', not for totals. Choose the scope: 'single' with account (the account NUMBER, e.g. '1020'), 'range' with from_account and to_account (account numbers), or 'all' for every account. Each row has the booking date, number and status, the description, the counterpart accounts, and debit / credit / running as integers in CENTS of the home currency — divide by 100 and present francs with two decimals. Rows with is_opening true are the account's starting balance, not a movement. Only the FIRST page of rows is returned: items_total is how many movements match in total, items_shown how many you can see. When items_total is larger than items_shown, say so and offer to narrow the dates instead of summing the rows you got — for totals, use the balance sheet or income statement.

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": {
      "scope": "<scope>",
      "date_from": "<date_from>",
      "date_to": "<date_to>",
      "company_id": "<company_id>"
    },
    "name": "get_account_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeYes'single' for one account, 'range' for a band of account numbers, 'all' for every account.
accountNoscope 'single': the account's number or id.
date_toYesEnd of the period, YYYY-MM-DD, inclusive.
date_fromYesStart of the period, YYYY-MM-DD, inclusive.
company_idYesThe company to work on — one of list_my_companies' company_id values.
to_accountNoscope 'range': the last account number in the band.
from_accountNoscope 'range': the first account number in the band.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Although annotations already declare this a read-only, idempotent, non-destructive operation, the description adds behavior the annotations cannot: only the first page is returned, items_total vs items_shown semantics, and how to behave when they diverge. It also discloses that is_opening rows are starting balances rather than movements, and that amounts are integer cents — all of which prevent misinterpretation of results.

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?

Purpose is front-loaded, then scope selection, then row shape, then pagination caveat — a sensible order with no filler sentences. It is a dense single block, so a reader must parse a lot of clauses, but every clause carries operational information.

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?

There is no output schema, and the description compensates fully by describing the returned row fields (booking date, number, status, description, counterpart accounts, debit/credit/running), their units, and the truncation fields. For a 7-parameter, 3-scope listing tool this leaves nothing essential unstated.

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 real meaning: the scope enum is mapped to which companion parameters apply ('single' with account, 'range' with from_account/to_account, 'all' for everything), and it clarifies that account is a NUMBER such as '1020' rather than an opaque id. It stops short of adding format guidance beyond the schema's YYYY-MM-DD notes.

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?

The description opens with a specific verb and resource ('movements of one or more accounts over a date range ... flat list of ledger rows with a running balance') and explicitly contrasts itself with the aggregate siblings ('not for totals'). An agent can distinguish it from get_journal, get_balance_sheet, and get_income_statement without opening any 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?

It names when to use it ('what happened on account X'), when not to (totals), and the concrete alternative ('use the balance sheet or income statement'). It also gives in-flow guidance for the truncated-results case: tell the user and offer to narrow dates rather than summing partial rows.

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

All YESbusiness toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources