Calcula saldo do FGTS, rendimento, saque-aniversário e multa rescisória de 40%. Atualizado 2026. Parâmetros obrigatórios: salary, months_worked. Opcionais: include_anniversary_withdrawal. Use exatamente estes nomes, em inglês.
| Name | Required | Description | Default |
|---|---|---|---|
| salary | Yes | Salário bruto mensal em R$ | |
| months_worked | Yes | Meses trabalhados | |
| include_anniversary_withdrawal | No | Calcular saque-aniversário? |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses currency ('Atualizado 2026') and enumerates computed components, which is useful. Still, it does not mention assumptions (e.g., 8% contribution rate), limitations, or whether results are estimates, leaving the behavior only partly transparent.
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 compact and front-loaded, with no filler. Each sentence earns its place: what is calculated, the 2026 update, required/optional parameters, and the naming caution.
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 3-parameter calculator with no output schema, the description lists the expected outputs and parameter requirements, which is decent. But it omits relevant boundary conditions, assumptions about FGTS rules, and any pointer to related tools, leaving some context gaps.
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 100%, so the schema already fully documents salary, months_worked, and include_anniversary_withdrawal. The description reinforces required/optional status and naming conventions but adds little semantic meaning beyond the schema.
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 ('Calcula') with a clear resource (FGTS) and enumerates the exact outputs: saldo, rendimento, saque-aniversário, and multa rescisória de 40%. This level of specificity distinguishes it from other calculate_* siblings, even without naming them.
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 clearly states which parameters are required versus optional and insists on exact English names, which helps invocation. However, it does not guide the agent on when to choose this tool over closely related siblings like calculate_antecipacao_fgts or calculate_custo_demissao; selection context is only implied.
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.
Many tools are clearly distinct, but the set contains several near-identical clusters: calculate_dividend_income_goal and calculate_dividend_yield both answer 'how much capital is needed to reach a dividend income target', and calculate_real_salary, calculate_raise_vs_inflation, and calculate_salary_time_value overlap heavily on salary/inflation comparisons. Generic tools like compare_investments and compare_with_cdb also blur the boundary with the many specific yield calculators.
Most tools follow a clear verb_noun snake_case pattern with verbs like calculate_, get_, check_, compare_, and advise_. However, the object language is inconsistent (calculate_ganho_capital_imovel alongside calculate_car_affordability), and can_i_quit_job breaks the command-style pattern with a question.
At 114 tools, the server is extremely over-scoped for an MCP surface; an agent cannot reasonably hold all these options in context. The inclusion of a search_calculator tool to route among the others is a strong signal that the tool set itself needs partitioning.
The surface is very comprehensive for Brazilian personal finance: employment, taxes, investments, debt, real estate, vehicles, small business, insurance, and market-data queries are all covered. A few minor gaps exist, such as no dedicated generic boleto-fine calculator or consolidated investment comparison engine, but no core workflow feels badly stranded.
