Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit List Inventory Movements

merit_list_inventory_movements
Read-only

Lists inventory movements (receipts, issues, transfers between locations) for a given date period, optionally with item lines, to review stock activity in Estonian bookkeeping.

Instructions

Inventory movements (laoliikumised) in a period: receipts, issues and transfers between locations.

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": {
      "period_start": "<period_start>",
      "period_end": "<period_end>"
    },
    "name": "merit_list_inventory_movements"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (totals still cover all)
date_typeNoFilter on document date, or on when it was last changeddocument
period_endYesLast day, YYYY-MM-DD (periods over 3 months are fetched in pieces; max 36 months)
with_linesNoAlso each movement's rows (items, quantities, amounts)
period_startYesFirst day, YYYY-MM-DD

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 safety behavior is covered. The description adds useful scope detail that movements include receipts, issues and transfers between locations, but it does not explain pagination, the with_lines expansion, or operational caveats like the 3-month chunking noted only in the schema.

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?

The description is a single front-loaded sentence with no redundant wording. It is tight and efficient, even though routing guidance is absent.

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?

An output schema exists and the input schema is fully described, so return values and parameter mechanics do not need repeating. The description gives enough for an agent to understand the dataset, though it stops short of distinguishing this from merit_inventory_report and other reporting tools.

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%, and the schema already documents limit, date_type, period_start, period_end and with_lines thoroughly. The description only restates the period scope and adds no parameter meaning beyond what the schema provides.

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 specific resource (inventory movements) and enumerates contents (receipts, issues and transfers between locations) within a period. It does not explicitly use 'list' or contrast with merit_inventory_report, so sibling differentiation is left implicit rather than stated.

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 exclusions, and no explicit alternative such as merit_inventory_report or other inventory-related tools. The only usage context is implied by the period scope.

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