Skip to main content
Glama
easor

easor

by Markku-hur

Build tuloslaskelma (income statement) for a period

build_profit_and_loss_statement
Read-only

Build a fully computed Finnish profit and loss statement for a chosen accounting period, with official line items, presentation-sign euro figures, and separate listing of unrecognized accounts.

Instructions

Builds a fully-computed Tuloslaskelma for the given period — every official line with real activity (Kirjanpitoasetus Liite 1 kululajikohtainen-tuloslaskelma order; lines with no activity at all are omitted — subtotals like LIIKEVOITTO are always kept, even at 0), with real euro figures already in conventional presentation sign (revenue positive, costs negative, profit positive when profitable — NOT raw ledger signs). Use this instead of assembling a report by hand from lookup_chart_of_accounts_template — it always produces the same structure. fromDate and toDate must fall within the same accounting period (fiscal year) — this refuses otherwise rather than silently computing a wrong number. Any account the organization uses that isn't recognized by the bundled template is listed separately in unclassifiedAccounts (raw ledger sign there, not the presentation sign above), never silently folded into a line — check those before reporting a total.

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>",
      "fromDate": "<fromDate>",
      "toDate": "<toDate>"
    },
    "name": "build_profit_and_loss_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
toDateYesYYYY-MM-DD — period end
fromDateYesYYYY-MM-DD — period start
organizationNumberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so safety is covered, but the description goes well beyond them: line-omission rules (inactive lines dropped, subtotals like LIIKEVOITTO kept at 0), the presentation sign convention (revenue positive, costs negative), and the refusal behavior for cross-period dates. The only gap is that it does not mention response shape/size or pagination-style concerns, though for an aggregate statement that is minor.

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?

Front-loaded with the purpose and the core scoping rule, then layers on caveats. It is dense and parenthetical-heavy, which makes it slightly harder to scan, but nearly every clause carries operational information an agent would otherwise get wrong (sign convention, unclassified accounts, period constraint).

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?

With no output schema and only three parameters, the description carries the full burden and discharges it: it explains the returned structure, the sign convention of the figures, the omission rules, and the unclassifiedAccounts escape hatch with its differing sign convention. An agent could call this correctly and interpret the result without further documentation.

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 67% and the schema already documents fromDate and toDate formats, so baseline would be a 3. The description adds real meaning beyond the schema by imposing the same-fiscal-year constraint on the two date parameters. It says nothing extra about organizationNumber, which is the one parameter left purely to the schema.

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 and resource ('Builds a fully-computed Tuloslaskelma for the given period') and pins down the exact structure used (Kirjanpitoasetus Liite 1 kululajikohtainen order). This clearly separates it from siblings like build_balance_sheet and lookup_chart_of_accounts_template without the agent needing to open 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 Guidelines5/5

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

Explicitly names the alternative ('assembling a report by hand from lookup_chart_of_accounts_template') and states why to prefer this tool ('it always produces the same structure'). It also gives a hard usage precondition — fromDate and toDate must fall in the same fiscal year or the call is refused — which is exactly the when/when-not guidance an agent needs.

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