Skip to main content
Glama
iseppo

e-arveldaja MCP Server

by iseppo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Compute Account Balance

compute_account_balance
Read-onlyIdempotent

Calculate an account balance from journal postings with optional client, dimension, and date filters to support reconciliation and financial reporting.

Instructions

Compute account balance from journal postings with optional client/dimension/date filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
freshNoClear cached API/reference data first.
date_toNoEnd date (YYYY-MM-DD)
date_fromNoStart date (YYYY-MM-DD)
account_idYesAccount id from list_accounts. In the RIK chart the id is the account number itself (e.g. 2110, 8900).
clients_idNoFilter by client ID
include_entriesNoInclude individual entries in response (default false)
accounts_dimensions_idNoFilter to one dimension (sub-account) of the account, e.g. the Wise dimension of 1020. Dimension id from list_account_dimensions; must belong to account_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.29.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / accounts_dimensions_id
      Added value: +{
+  "description": "Filter to one dimension (sub-account) of the account, e.g. the Wise dimension of 1020. Dimension id from list_account_dimensions; must belong to account_id.",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}
  2. Addedv0.25.3
  3. Removedv0.25.2
  4. First observedv0.18.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, closed-world, so safety is covered. The description adds that the balance is derived from journal postings and that filters are optional, but says nothing about caching behavior (the 'fresh' param hints at caching) or result stability, so it adds only modest context.

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?

It is a single efficient sentence with the core action front-loaded. It is appropriately sized, though slightly thin given the tool's complexity.

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 read-only computation tool with full schema coverage and annotations, the description covers the essentials. However, it omits where the result can be retrieved, whether results are cached, and how it relates to sibling balance tools, leaving some gaps.

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 coverage is 100%, so the schema already documents all seven parameters in detail, including date formats, account_id semantics, and dimension filtering. The description merely echoes optional filters (client/dimension/date) without adding syntax or format details, so baseline 3 applies.

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 (Compute) and resource (account balance) plus inputs (journal postings). It distinguishes somewhat from compute_account_dimension_balances by naming the resource 'account', but does not explicitly call out the sibling, so it's clear yet not fully differentiated.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives like compute_account_dimension_balances or compute_trial_balance even though they are close siblings. Usage is only implied by the phrasing 'from journal postings'.

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