Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit Get Recurring Invoice

merit_get_recurring_invoice
Read-only

Retrieve a recurring invoice contract by ID to view its customer, payer, billing cycle, payment terms, and invoice rows.

Instructions

One recurring invoice contract in full: customer, payer, cycle, payment terms and rows.

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

Input Schema

NameRequiredDescriptionDefault
idYesSIHId from merit_list_recurring_invoices

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 that the response is the complete contract including line rows, which tells the agent the payload is broad. It says nothing about behavior on an unknown id, permissions, or latency, so it does not go beyond a modest addition.

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?

A single compact sentence with the scope and the returned contents front-loaded; no filler, no restatement of the title, and nothing that could be cut without losing information.

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?

With an output schema present and annotations covering safety, the description only needs to establish scope and payload shape, which it does by listing the included sections. A brief note on failure behavior for an invalid id would make it fully complete, but nothing essential is missing.

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% and the single id parameter is documented with its provenance ('SIHId from merit_list_recurring_invoices'), so the schema carries the semantic load. The description contributes no additional parameter meaning beyond what is already structured, which is the expected baseline here.

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 resource precisely ('recurring invoice contract') and scopes it to a single record ('One ... in full'), which implicitly separates it from merit_list_recurring_invoices. It goes on to enumerate the included content (customer, payer, cycle, payment terms, rows), so the agent knows this is a full-detail fetch rather than a summary.

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 implied rather than stated: 'One ... in full' suggests fetching details for an already-identified contract, and the schema's id description points at merit_list_recurring_invoices as the source of the identifier. There is no explicit when-to-use/when-not-to-use clause or named alternative in the description itself.

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