Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Antecipar parcelas

anticipate_installments

Move future installments from a series to a target billing period, applying an optional discount. Requires confirmation before executing.

Instructions

Move parcelas futuras de uma série para uma fatura alvo, aplicando desconto opcional. Exige confirm: true.

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": {
      "seriesId": "<seriesId>",
      "installmentIds": "<installmentIds>",
      "targetPeriod": "<targetPeriod>"
    },
    "name": "anticipate_installments"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
discountNo
seriesIdYes
targetPeriodYes
installmentIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this mutates state without being flagged destructive. The description adds real value by disclosing the mandatory confirm gate and the optional discount application, but it leaves out what happens to the source invoice, whether already-paid installments can be moved, and whether the operation is reversible. The described mutation is consistent with the annotations, so no contradiction.

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?

Two short sentences, front-loaded with the action and followed by the confirmation requirement; nothing is redundant or padded.

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?

This is a financially material mutation with five parameters, zero schema description coverage and no output schema, yet the description is only two sentences. It should at minimum cover discount units, the targetPeriod format, return/response expectations, and the recommended quote-then-commit flow.

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 description coverage is 0%, so the description must carry parameter meaning and only partly does: it links confirm (required), discount (optional), seriesId, installmentIds and targetPeriod to concepts. It never specifies whether discount is a percentage or an absolute amount, how installmentIds are selected among the series' future installments, or that targetPeriod is a YYYY-MM period rather than an invoice identifier ('fatura alvo' suggests an invoice object).

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?

States a concrete verb and resource: moving future installments of a series into a target invoice, with an optional discount. An agent can distinguish this from list_installments (enumeration) or quote_installments (simulation) by the verb 'move', but the description never names those siblings to make the distinction explicit, and the Portuguese text under an English tool name costs a moment of parsing.

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?

The intended use case is implied by the purpose itself, and it correctly flags the confirm: true gate. However there is no guidance on when this should be preceded by a quote/simulation, no preconditions (e.g. installment or series state), and no statement of when not to use it.

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