Skip to main content
Glama

get_gl_account_ledger

One account's ledger (Kontoauszug) — every booking that touched it, in date order, with Soll/Haben and the running balance after each line (CompanyMember).

No fiscal-year parameter: the chart is FY-owned, so account_id already fixes the year. Posted and reversed entries are included (a reversal is a second posted entry, so both legs must show or the balance is wrong); drafts are not. The running balance is carried across pages by the server — page_opening_balance enters this page's first row, while closing_balance/total_debit/total_credit describe the whole window. 404 when the account is not this company's; 422 when date_from is later than date_to.

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": {
      "company_id": "<company_id>",
      "account_id": "<account_id>"
    },
    "name": "get_gl_account_ledger"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
date_toNo
date_fromNo
account_idYes
company_idYes
dimension_value_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / dimension_value_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 21,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it explains entry inclusion rules (posted and reversed yes, drafts no, with the reason the reversal legs must appear), states that the server carries the running balance across pages, and defines page_opening_balance versus closing_balance/total_debit/total_credit as different scopes. Error semantics (404 for wrong company, 422 for inverted date range) are also disclosed, which is behavior beyond anything a schema could convey.

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?

The core statement is front-loaded, and the following sentences on year scoping, inclusion rules, balance fields, and errors are each substantive. It is dense and parenthetical-heavy (German terms, backticked field names) but not padded; little could be removed without losing real information.

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?

For a 7-parameter tool with no annotations and no output schema, the definition is unusually complete on return-value semantics and edge cases, but it omits any explanation of pagination controls and the dimension_value_id filter, leaving a real gap in how an agent would call it correctly with filtering or paging.

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 0% across 7 parameters, so the description must compensate and it largely does not: it covers only account_id (implicitly, via the fiscal-year note) and date_from/date_to (via the 422 rule). company_id, limit, offset, and especially dimension_value_id — a filter whose meaning is entirely undocumented — are left undefined in both schema and description.

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?

"One account's ledger (Kontoauszug) — every booking that touched it, in date order, with Soll/Haben and the running balance after each line" states a specific verb+resource, the scope (single account), the ordering, and the distinctive output (running balance). An agent can immediately distinguish this from a journal-entry or trial-balance style tool without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Strong contextual guidance: no fiscal-year parameter is needed because account_id fixes the year, posted and reversed entries are included while drafts are not, and 404/422 conditions are spelled out. It stops short of naming a concrete alternative (e.g. list_gl_journal_entries for drafts or cross-account queries), which keeps it at 4 rather than 5.

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