Skip to main content
Glama
iseppo

e-arveldaja MCP Server

by iseppo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Book Lightyear Distributions

book_lightyear_distributions
Destructive

Create journal entries for Lightyear dividend, interest, and reward distributions, including withheld tax. Preview changes with default dry run.

Instructions

Create journal entries for Lightyear dividend, interest, and reward distributions, including withheld tax. DRY RUN by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNoPreview without creating entries (default true)
file_refNoOpaque Lightyear AccountStatement file reference.
file_pathNoAccountStatement path/base64 input. Provide exactly one of file_path or file_ref.
fee_accountNoPlatform fee expense account (default 8610 Muud finantskulud)
plan_handleNoExecution-plan handle from the reviewed dry run. Required for dry_run=false.
tax_accountNoWithheld tax receivable/expense account (for tax_amount from CSV)
broker_accountYesBroker cash account (e.g. 1120 Lightyear konto)
income_accountYesIncome account for Dividend rows (dividends from directly-held shares → 8330 'Tulu aktsiatelt ja osadelt'). Fund Distribution rows use fund_distribution_account and Interest rows use interest_account.
reward_accountNoAccount for platform rewards/bonuses (default: auto-detect 'Muud finantstulud', standard 8600). Rewards are broker fee/campaign income, not securities income.
interest_accountNoAccount for Interest rows (default: auto-detect 'Intressitulu hoiustelt', standard 8400).
broker_dimension_idNoDimension ID for broker account (accounts_dimensions_id)
fund_distribution_accountNoAccount for fund Distribution rows (default: auto-detect 'Tulu fondiosakute ümberhindlusest', standard 8320).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.29.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed3 schema fields changedv0.27.0
    • addedInput schema / properties / fund_distribution_account
      Added value: +{
+  "description": "Account for fund Distribution rows (default: auto-detect 'Tulu fondiosakute ümberhindlusest', standard 8320).",
+  "type": "number"
+}
    • changedInput schema / properties / income_account / description
      Previous value: -"Investment income account for the distribution. Dividends from directly-held shares → 8330 'Tulu aktsiatelt ja osadelt'; fund distributions → 8320; interest → 8400."New value: +"Income account for Dividend rows (dividends from directly-held shares → 8330 'Tulu aktsiatelt ja osadelt'). Fund Distribution rows use fund_distribution_account and Interest rows use interest_account."
    • addedInput schema / properties / interest_account
      Added value: +{
+  "description": "Account for Interest rows (default: auto-detect 'Intressitulu hoiustelt', standard 8400).",
+  "type": "number"
+}
  3. Changed6 schema fields changedv0.25.2
    • changedInput schema / properties / file_path / description
      Previous value: -"Absolute path to Lightyear AccountStatement CSV file."New value: +"AccountStatement path/base64 input. Provide exactly one of file_path or file_ref."
    • addedInput schema / properties / file_ref
      Added value: +{
+  "description": "Opaque Lightyear AccountStatement file reference.",
+  "type": "string"
+}
    • changedInput schema / properties / income_account / description
      Previous value: -"Investment income account (e.g. 8320 Tulu fondiosakutelt, 8400 Intressitulu)"New value: +"Investment income account for the distribution. Dividends from directly-held shares → 8330 'Tulu aktsiatelt ja osadelt'; fund distributions → 8320; interest → 8400."
    • addedInput schema / properties / plan_handle
      Added value: +{
+  "description": "Execution-plan handle from the reviewed dry run. Required for dry_run=false.",
+  "type": "string"
+}
    • changedInput schema / properties / reward_account / description
      Previous value: -"Account for platform rewards (default: 3800 Muud äritulud). Rewards are non-investment income."New value: +"Account for platform rewards/bonuses (default: auto-detect 'Muud finantstulud', standard 8600). Rewards are broker fee/campaign income, not securities income."
    • changedInput schema / required
      Previous value: -[
-  "file_path",
-  "broker_account",
-  "income_account"
-]New value: +[
+  "broker_account",
+  "income_account"
+]
  4. First observedv0.18.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare write, destructive, non-idempotent, and open-world behavior, but the description adds the important default dry-run behavior and notes that withheld tax is handled. It does not explain the destructive impact of non-dry execution or remediation steps, so it falls short of fully rich behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler. The action and scope are front-loaded, and the critical dry-run default is stated immediately after, making the description easy to scan.

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 12-parameter mutation tool with no output schema, the description covers purpose and the key safety default but omits workflow context: that an AccountStatement file is required and that a reviewed dry-run plan is needed before execution. The rich schema compensates for missing parameter details, but the two-step dry-run/execute process is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all 12 parameters are thoroughly documented in the input schema, including defaults and account mappings. The description adds only high-level distribution types and tax handling, not parameter-level syntax or constraints, so the baseline 3 is appropriate.

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 scope: 'Create journal entries for Lightyear dividend, interest, and reward distributions, including withheld tax.' This clearly distinguishes it from sibling tools like book_lightyear_trades and parse_lightyear_statement by focusing on distribution booking, though it does not name those alternatives explicitly.

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

Usage Guidelines2/5

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

The only guidance is 'DRY RUN by default,' which hints at a preview-first workflow but does not explain when to use this tool versus alternatives such as book_lightyear_trades or parse_lightyear_statement. No prerequisites, exclusions, or explicit when/when-not instructions are provided.

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

Deploy Server

Other Tools