Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit List Fixed Assets

merit_list_fixed_assets
Read-only

List fixed asset records with acquisition cost, accumulated depreciation, remaining value, location, and responsible person in EUR; filter by name, inventory number, or group.

Instructions

Fixed assets (põhivara): acquisition, depreciation so far, remaining value, location and responsible person. Amounts in EUR.

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_list_fixed_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (totals still cover all)
searchNoOnly assets whose name, inventory number or group contains this

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 is covered. The description usefully adds that amounts are denominated in EUR and glosses the local term 'põhivara', but says nothing about scope limits, totals behavior, or result size — the schema's 'totals still cover all' note is the only hint of that.

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 dense sentence with the resource front-loaded and the currency constraint appended, no filler. It could be marginally tighter, but nothing is wasted.

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 shape needn't be described, and both optional parameters are documented in the schema. Still, for a paginated list tool the description leaves unanswered whether results are truncated or ordered, information an agent needs to call it confidently at scale.

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%, so both optional parameters are fully self-documenting. The description adds no meaning about limit/search interaction or how search matching is scoped, which keeps it at the baseline 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?

Names the specific resource and enumerates what it carries: acquisition, depreciation so far, remaining value, location, responsible person. That is well beyond a restatement of the name, though it never uses an explicit verb like 'list' and does not distinguish crude entity scope from siblings such as merit_list_inventory_movements — the entity type does that implicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer it should call this when it needs fixed-asset data, and no sibling covers fixed assets. There is no explicit when-to-use statement, no exclusions, and no pointer to alternatives for related needs (e.g. balance sheet totals).

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