Skip to main content
Glama
Sign In
OpenMonetis MCP

OpenMonetis MCP

by Welington98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Cotar antecipação de parcelas

quote_installments
Read-onlyIdempotent

Calculates the number and total value of selected installments from their IDs, so you can verify amounts before advancing them to a credit card statement.

Instructions

Calcula quantidade e valor total das parcelas informadas — usado antes de antecipar para uma fatura.

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": {
      "installmentIds": "<installmentIds>"
    },
    "name": "quote_installments"
  }
}

Input Schema

NameRequiredDescriptionDefault
installmentIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

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, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds that this is a pre-anticipation calculation step, which is useful workflow context, but says nothing about the shape of the result beyond count and total, nor about error behavior for invalid installment IDs.

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 front-loaded sentence that states the computation first and the usage context second, with no filler. It is appropriately sized, though the em-dash clause is slightly compressed for the amount of meaning it carries.

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?

There is no output schema, and the description partially compensates by naming the two returned quantities (count and total value). However, for a tool whose only parameter is entirely undocumented and whose return shape matters for a financial decision, the definition leaves meaningful gaps.

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 0% and the single parameter, installmentIds, is never explained. "Parcelas informadas" only vaguely gestures at the input; the description does not say that the parameter is an array of installment UUIDs, that at least one is required, or what happens with IDs from mixed invoices. With zero schema documentation, the description should have compensated and does not.

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 states a specific verb ("Calcula") and resource ("quantidade e valor total das parcelas") and frames itself as the calculation step that precedes anticipation, which implicitly separates it from anticipate_installments. It is clear what the tool computes, though it never explicitly names the sibling it precedes.

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

Usage Guidelines4/5

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

The clause "usado antes de antecipar para uma fatura" gives concrete usage context: call this as a preview before the anticipation operation. There are no explicit exclusions or a named alternative, but the ordering guidance is unambiguous enough for an agent to sequence calls correctly.

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

Deploy Server

Other Tools