Calcula o imposto sobre prêmios de apostas esportivas e bets (Lei 14.790): 15% sobre os ganhos LÍQUIDOS do ano (prêmios menos apostas) no que passar da isenção da primeira faixa da tabela anual do IRPF. Parâmetros obrigatórios: annual_prizes, annual_stakes. Use exatamente estes nomes, em inglês.
| Name | Required | Description | Default |
|---|---|---|---|
| annual_prizes | Yes | Total de prêmios recebidos no ano, em R$ | |
| annual_stakes | Yes | Total apostado no ano, em R$ |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. It goes beyond a tautology by disclosing the calculation basis (15% on net annual gains above the IRPF exemption) and the legal foundation. It stops short of describing the return contract, but the core behavior is well disclosed.
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 dense sentences with the key formula front-loaded and parameter instructions after; no filler or redundant explanation.
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 deterministic calculator with two scalar inputs, the description plus schema is sufficient to select and invoke correctly. The only mild omission is the explicit output shape or zero-loss behavior, but no output schema exists and the computed value is strongly implied.
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?
Both parameters already have full Portuguese schema descriptions with units (R$), so the description adds limited semantic value. It reinforces that the names must be used exactly and that they are mandatory, but this largely duplicates the schema's required array.
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'), names the resource ('imposto sobre prêmios de apostas esportivas e bets'), and even states the rate and legal basis (Lei 14.790). This clearly distinguishes it from the many other calculate_* tax siblings.
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?
It clearly identifies the intended context — annual betting/gambling prize taxation — and explicitly designates the two required parameters. It does not name alternatives or exclusions, so it falls short of full when/when-not guidance.
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.
