Revisional de contrato bancário: recalcula o financiamento pela taxa média de mercado do BACEN (busca ao vivo por modalidade+mês) e apura o excedente por parcela (Price ou SAC). A taxa média é referência, não teto (STJ).
| Name | Required | Description | Default |
|---|---|---|---|
| sistema | No | ||
| modalidade | No | ||
| num_parcelas | Yes | ||
| parcela_paga | Yes | ||
| data_contrato | No | ||
| taxa_bacen_am | No | ||
| valor_financiado | Yes | ||
| taxa_contratada_am | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already establish readOnlyHint, idempotentHint, and destructiveHint. The description adds meaningful behavioral detail: it performs a live BACEN rate lookup by modality+month, uses Price or SAC systems, and clarifies that the average rate is a reference, not a ceiling (STJ legal context). No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no filler. The first sentence front-loads the core calculation and method, and the second adds a critical legal caveat. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only calculation tool with no output schema, the description covers the algorithm, data sources, systems, and a legal nuance. It does not explain return value shape or date formats, but the mention of 'apura o excedente por parcela' gives a reasonable expectation of the output. Given the tool's complexity, this is nearly complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It semantically covers several parameters (modalidade, mês/data_contrato, Price or SAC, parcela, financiamento), but it does not explicitly define each parameter or their units. The Portuguese parameter names are self-explanatory, but the description does not fully replace missing schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('recalcula') and a specific resource ('financiamento' via BACEN average rate), and adds scope ('Revisional de contrato bancário'). It clearly distinguishes this tool from siblings like calculo_aluguel or calculo_fgts by describing the bank-contract review use case and the Price/SAC surplus calculation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear usage context: it is for recalculating a bank loan under the BACEN average rate and computing the surplus per installment. It does not explicitly name alternatives or when not to use it, but the domain is specific enough that an agent can infer appropriate use from the 'Revisional de contrato bancário' framing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The 16 calculation tools are each tied to a distinct legal scenario (rent, criminal sentencing, FGTS, labor severance, etc.), so misselection is unlikely. However, the platform meta-tools overlap: connect, toolkit_info, and authenticate all deal with connection/auth state, and marketplace's list_tools/describe overlaps with toolkit_info.
The legal calculators use a consistent calculo_<domain> prefix, which is highly predictable. But the six meta-tools use standalone English names (connect, marketplace, report_bug) and the prefix itself mixes nouns (calculo_aluguel) with a verb (calculo_atualizar), so the overall convention is not uniform.
22 tools is on the heavy side for a server claiming to be about 'juros e multa', especially since six tools are unrelated platform administration features. The 16 legal calculators are arguably well-scoped, but the meta-tool wrapper inflates the count and blurs the server's purpose.
The legal calculation surface is unusually broad: civil, criminal, labor, social security, banking, and family law are all represented, and the calculo_atualizar tool provides the generic debt-update/interest/fee calculation implied by the server name. Minor gaps exist—there is no dedicated simple-interest-only calculator or court-fees/custas calculator—but no obvious dead-end workflows remain.