Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit Inventory Report

merit_inventory_report
Read-only

Retrieves stock-on-hand quantities, prices, and values per item and location for a chosen date, with filters for zero stock, item groups, and sales-order reservations.

Instructions

Stock on hand (laoseis) per item and location on a date, with quantity, price and value.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "merit_inventory_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoStock on this date, YYYY-MM-DD; default today
limitNoMax rows to return (totals still cover all)
locationNoOnly this inventory location, code or name
show_zeroNoAlso items with zero stock
item_groupsNoOnly these item group codes (merit_reference_list kind=item_groups)
with_reservationsNoAlso quantities reserved by sales orders

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 context about what the report contains (quantity, price, value per item and location at a date), but omits behavioral traits like the fact that limit truncates rows while totals still cover all items, or that reservations are opt-in. With annotations carrying the read-only signal, a 3 is appropriate.

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 efficient sentence with the core resource front-loaded and no filler or redundancy. It is well-structured for scanning, though its brevity comes at the cost of the guidance scored elsewhere.

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?

An output schema exists, so return-value explanation is not required, and all six parameters are fully documented in the schema. What remains missing is usage context relative to sibling reporting tools and any note about totals-vs-rows behavior, leaving the definition adequate but not complete for a report tool in a crowded reporting family.

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 every parameter (as_of, limit, location, show_zero, item_groups, with_reservations) is already documented in the schema. The description's phrase 'on a date' loosely maps to as_of but adds no format, default, or interaction details beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 (stock on hand / laoseis) with clear scope: per item and location, on a date, with quantity, price and value. An agent can tell this is a point-in-time inventory valuation snapshot. It does not explicitly contrast with merit_list_inventory_movements, but the 'on a date' snapshot framing is distinct enough to be actionable.

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 mention of when to prefer this over the movements report or reference lists, and no stated preconditions. The agent must infer that this is the stock-balance view rather than a transaction history view from the description wording alone.

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