Skip to main content
Glama
easor

easor

by Markku-hur

Get general ledger events

get_general_ledger_events
Read-only

Retrieve paginated general ledger postings, optionally filtered by date, account, or category, to review individual credits and debits and build accurate accounting reports or reconciliations.

Instructions

Returns a page of general ledger events (individual postings), optionally filtered. When summing postings for a total, use (credit ?? debet ?? 0) per posting — NEVER credit - debet or debet - credit. credit and debet are mutually exclusive per posting and already correctly signed (credit negative, debet positive); subtracting one from the other double-applies the sign. This matters most when an account has both kinds of posting in the period (e.g. a sale immediately reversed same-day) — an account with only one kind can look reconciled even with a wrong formula.

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": {
      "organizationNumber": "<organizationNumber>",
      "pageIndex": "<pageIndex>",
      "pageSize": "<pageSize>"
    },
    "name": "get_general_ledger_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toDateNo
categoryNo
fromDateNo
pageSizeYes
pageIndexYes
externalAuditNoValue for the x-External-Audit header
accountNumbersNoComma-separated account numbers
organizationNumberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover read-only safety, and the description adds genuinely valuable behavioral context: results are paginated, credit and debet are mutually exclusive per posting and pre-signed (credit negative, debet positive). It does not cover page limits, total counts, or the externalAudit header requirement, but the sign-disclosure is substantive beyond the annotations.

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 in the first clause, followed by a clearly motivated warning. The sign convention is restated three ways (never credit - debet, mutually exclusive and pre-signed, double-applies the sign), which is slightly redundant but the final sentence adds a distinct failure-detection point.

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?

With no output schema, the description usefully explains how to interpret posting amounts, but an 8-parameter, 25%-coverage input schema is left largely unaddressed, and pagination behavior (returned page metadata, how to continue) is never described.

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 only 25% across 8 parameters, and the description explains none of them — not fromDate/toDate, category, accountNumbers, organizationNumber, or pagination. The credit/debet discussion concerns returned fields rather than inputs, so it does not compensate for the parameter gap.

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: returns a page of general ledger events, explicitly clarified as individual postings, optionally filtered. This distinguishes it well from aggregate siblings like build_balance_sheet and build_profit_and_loss_statement, though those alternatives are never named.

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?

Provides strong guidance on how to consume the results (how to sum postings correctly) but says nothing about when to pick this tool over the balance sheet or P&L builders, nor about prerequisites such as organization selection. Usage context is implied rather than stated at the selection level.

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