Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit Balance Sheet

merit_balance_sheet
Read-only

Generate a month-end balance sheet in EUR for a specified month, optionally comparing previous months and showing account-level details.

Instructions

Statement of financial position (bilanss) at month-end, in EUR.

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": {
      "month": "<month>"
    },
    "name": "merit_balance_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthYesBalance at the end of this month, YYYY-MM
show_accountsNoAlso show each line's accounts
compare_monthsNoAlso show this many previous month-ends

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description usefully adds that values are in EUR and anchored to month-end. Beyond currency and period, it discloses nothing about how previous months are aggregated via compare_months or what the returned structure covers, which the existing output schema partly absorbs.

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?

A single front-loaded sentence covering resource, timing, and currency with zero filler. It is tightly written, though the extreme brevity borders on under-specification rather than maximal efficiency.

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 a full input schema, an output schema, and read-only annotations, the missing pieces are modest, but a financial statement tool would benefit from noting period conventions and what compare_months returns. The definition is adequate rather than complete.

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%, with each of the three parameters documented inline (YYYY-MM month, show_accounts, compare_months). The description adds no meaning beyond that, so the 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?

The description names a precise resource ('Statement of financial position (bilanss)') and scopes it to month-end in EUR, so an agent knows exactly what report this produces. It stops short of explicitly differentiating itself from siblings such as merit_profit_and_loss, leaving that distinction to be inferred from the resource name alone.

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 when-to-use guidance, no prerequisites, and no mention of alternatives or exclusions. The agent must infer from the single noun phrase that this is the report to pick for balance-sheet data.

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