Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit Profit And Loss

merit_profit_and_loss
Read-only

Generates a monthly profit and loss statement in EUR with one column per calendar month and a total column, optionally listing accounts per line.

Instructions

Profit and loss statement (kasumiaruanne) by calendar month, in EUR, with a total column.

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": {
      "last_month": "<last_month>"
    },
    "name": "merit_profit_and_loss"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsNoNumber of months, one column each
last_monthYesLast month in the report, YYYY-MM
show_accountsNoAlso show each line's accounts

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, so the safety profile is covered. The description adds useful report-shape context — EUR currency, calendar-month columns, and a total column — but says nothing about data freshness, permissions, or pagination/size limits.

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 with no wasted words; the resource and its key output characteristics come first. It is terse to the point of omitting usage guidance, but nothing in it is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (3 fully described parameters, an output schema that covers return values) and the description states currency, granularity and total column. The only real gap is routing guidance against sibling reports, which for a self-evidently named financial statement is a minor omission.

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% with per-parameter descriptions for months, last_month and show_accounts, so the schema carries the load. The description reinforces that months become one column each, but adds no format or edge-case detail beyond that.

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 resource (profit and loss statement), its local name (kasumiaruanne), the reporting granularity (by calendar month), currency (EUR) and shape (total column). An agent can distinguish it from merit_balance_sheet and the other merit_* reports by resource, though it never explicitly contrasts with them.

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 when another report (e.g. balance sheet, sales report) would be the better choice. Usage is only implied by the resource name.

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