Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit Get Gl Batch

merit_get_gl_batch
Read-only

Retrieve a single general ledger batch by GLBId to view its debit and credit lines per account, optionally including attachments.

Instructions

One general ledger entry with its debit and credit lines per account.

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": {
      "id": "<id>"
    },
    "name": "merit_get_gl_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesGLBId from merit_list_gl_batches
include_attachmentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. With no output schema, the phrase about debit/credit lines per account is a modest contribution by sketching the returned record's shape, but nothing is said about attachment retrieval, error behavior, or scoping.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler, but it is under-specified rather than economical — it spends its one clause describing the payload instead of leading with what the tool does.

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

Completeness2/5

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

For a fetch-by-id tool with no output schema and a parameter whose purpose is unexplained, the description leaves too much unsaid: no verb, no mention of attachments, no note that a single batch is returned for the given id.

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

Parameters2/5

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

Schema coverage is 50%: id is documented (including its source), but include_attachment has only a default and no explanation anywhere. The description says nothing about either parameter, so the undocumented half stays undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence names the resource ('general ledger entry with its debit and credit lines per account') and implies a single item via 'One', which does distinguish it somewhat from merit_list_gl_batches. But it never states the verb (retrieve/fetch) and reads like a description of the returned object rather than of the tool's action.

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?

No guidance on when to use this versus merit_list_gl_batches or the other get_* siblings. The only routing hint (that the id originates from merit_list_gl_batches) lives in the schema, not the description.

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