Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit Reference List

merit_reference_list
Read-only

Retrieves bookkeeping master data such as accounts, VAT rates, departments, items, and payment types by category, with optional search filtering.

Instructions

Master data: chart of accounts, bank accounts, VAT rates, departments, dimensions, items, financial years, customer, vendor and item groups, units of measure, payment types (what a purchase, expense report or sale can be paid from or to), inventory locations, fixed asset locations and responsible employees.

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": {
      "kind": "<kind>"
    },
    "name": "merit_reference_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
searchNoOnly rows whose code or name contains this

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/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 and the description's bar is lower. Beyond that, the description says nothing about behavior an agent would want: result volume (these sets can be large), ordering, whether 'search' is server-side filtered, or whether any kind requires extra permissions. It adds only domain naming, not behavior.

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?

One front-loaded sentence with the resource category stated first and the enumeration second; every list item earns its place by disambiguating an enum value. The parenthetical for payment types is the one slightly verbose element, but it prevents a likely misuse.

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 an output schema present, return values need not be described, and for a two-parameter reference-data read the definition covers the essentials. It is still missing what an agent needs to call it confidently at scale: whether results are paginated or complete, and why to pick this over the find_* siblings for customer/vendor lookups.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, with 'search' documented in the schema but 'kind' enum values left bare. The description compensates well by expanding each terse enum value into a meaningful label ('accounts' -> chart of accounts, 'taxes' -> VAT rates, 'units' -> units of measure, 'fixed_asset_responsible' -> responsible employees), which is genuine meaning beyond the schema. It stops short of saying whether search is case-sensitive or matches both code and name (the schema handles that) or of mapping items in enum order, so a 4 rather than a 5.

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 gives a specific verb-plus-resource framing ('Master data:') and enumerates the 15 reference kinds the tool returns, so an agent can tell it lists static configuration data rather than transactions. It does not, however, distinguish itself from siblings like merit_find_customers or merit_find_vendors, and the phrase 'customer, vendor and item groups' is only disambiguated by the enum, so a careless reader could mistake this for a customer/vendor lookup.

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 statement of when to use this tool versus the many merit_list_* or merit_find_* siblings, and no exclusions. The only usage hint is implicit domain context ('what a purchase, expense report or sale can be paid from or to' for payment types), which explains a value but not when to call the tool.

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