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 cover read-only, idempotent, and non-destructive behavior. The description adds meaningful context beyond those annotations by disclosing a live BACEN rate lookup depencency and the legal nuance that the average rate is a reference, not a ceiling. This is useful behavioral information for an agent.
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?
The description is concise and front-loaded: it states the purpose in the first few words, then adds live-lookup and legal context in two tight sentences. Every sentence contributes useful information without repetition or filler.
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?
With no output schema and 8 parameters, the description covers the core purpose and an important legal caveat, but it does not describe the return structure or clarify optional inputs like taxa_bacen_am as an override versus the live lookup. It is adequate for basic invocation but leaves gaps for a fully autonomous agent.
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 clarifies the roles of sistema (Price or SAC), modalidade+mês for the live lookup, and the concept of excedente por parcela. However, it does not explain key parameters like taxa_bacen_am, data_contrato, valor_financiado, or parcela_paga, relying mostly on their self-evident names.
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 specific verbs and resources: 'recalcula o financiamento' and 'apura o excedente por parcela', and identifies the distinctive BACEN market-rate calculation. It clearly distinguishes this tool from the many other calculo_ siblings by focusing on bank-contract revisional calculations.
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 frames the exact use case: revisional de contrato bancário with BACEN average rates, which gives a routing agent a clear context for selecting it. However, it does not explicitly name alternatives or state when not to use this tool, so it falls short of the highest bar.
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 calculo_* tools are each tied to a specific legal area and are generally easy to distinguish. However, the platform tools overlap: marketplace bundles discovery, auth, listing, and bug-report flows that also exist in authenticate, connect, toolkit_info, and report_bug.
The calculo_* group is highly consistent and readable. The six platform tools follow a different, more mixed English convention with bare verbs, noun phrases, and snake_case names, so the set as a whole has two naming schemas rather than one.
22 tools is in the heavy 16-25 range and feels excessive for a server titled 'Reajuste de Aluguel'. Some legal calculators are useful in a broader legal-calculation platform, but the title and the actual scope are mismatched.
For a broad Brazilian legal-calculation toolkit, coverage is quite wide: rent, monetary updating, criminal sentencing, FGTS, INSS, labor, and banking calculations are present. Still, there are notable gaps for a general legal surface, such as other INSS benefit calculations or civil compensation estimates, and the rent-adjustment title does not represent the full set.