Skip to main content
Glama

FalaZuki Finance BR

start_investing

Quero começar a investir. Encadeia, a partir do dinheiro de hoje, do aporte mensal, dos gastos do mês e de uma meta: a reserva de emergência (quanto do dinheiro de hoje e do aporte vai para ela e em quantos meses ela fecha), o mesmo valor e prazo no Tesouro Selic, num CDB e numa LCI lado a lado, bruto e líquido, o imposto de renda regressivo no resgate (LCI e LCA isentas para pessoa física, Lei 11.033/2004, art. 3º), os valores descontado o IPCA e o tempo até a meta com o aporte mensal, como na calculadora do milhão. Os números saem lado a lado, sem escolher aplicação; o que falta de taxa sai como pulado, com o motivo.

Input Schema

NameRequiredDescriptionDefault
monthsYesPrazo da comparação entre as aplicações, em meses (1-360)
cdi_annualNoCDI ao ano, em %. Sem ele, CDB e LCI não são simulados
goal_amountYesA meta de patrimônio, em R$ nominais
ipca_annualNoInflação anual em % (ex: o IPCA de 12 meses). Sem ela, os valores reais não são calculados
selic_annualNoSelic ao ano, em %. Sem ela, o Tesouro Selic não é simulado
initial_amountYesDinheiro disponível hoje para guardar e investir, em R$
reserve_monthsNoQuantos meses de gastos a reserva deve cobrir
cdb_cdi_percentNoPercentual do CDI que o CDB paga (100 = CDI cheio)
lci_cdi_percentNoPercentual do CDI que a LCI ou LCA paga (ex: 90)
monthly_expensesYesGastos de um mês, em R$: a base da reserva
goal_annual_returnNoRentabilidade anual em % usada no tempo até a meta (8 = padrão da calculadora do milhão)
monthly_contributionYesQuanto consegue guardar por mês, em R$

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does disclose meaningful behavior: outputs are presented side by side without picking a recommended application ('sem escolher aplicação'), and any missing rate input produces a skipped result with a reason ('o que falta de taxa sai como pulado, com o motivo'). It also states gross/net and regressive-IR handling. It stops short of describing output shape or ordering, but adds real context beyond a bare schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the intent ('Quero começar a investir') and most content is substantive for such a composite tool, but it is delivered as a single sprawling sentence with nested parentheses, which hurts readability and scan-ability. Appropriately sized, poorly structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter composite calculator with no output schema and no annotations, the description does a good job enumerating the outputs (reserve, side-by-side applications, gross/net, IPCA-adjusted values, time to goal) and the skip-with-reason behavior. It could be clearer on output structure, but an agent has enough to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 12 parameters, including the conditional behavior for missing selic/cdi/ipca. The description adds the narrative linkage between initial_amount, monthly_contribution, monthly_expenses and goal_amount, but no syntax, units, or defaults beyond what the schema provides, so the baseline 3 applies.

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 conveys a specific composite purpose: chain an emergency-reserve calculation, a side-by-side Tesouro Selic / CDB / LCI comparison (gross and net, with regressive IR), real (IPCA-discounted) values, and time-to-goal. It is detailed enough to know what the tool produces, but it never names or differentiates itself from the many overlapping siblings (calculate_emergency_fund, compare_investments, calculate_first_million).

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

Usage Guidelines3/5

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

'Quero começar a investir' implies the scenario (someone starting to invest with today's cash, a monthly contribution and a goal), which gives implied usage context. However, there is no explicit when-to-use, no when-not-to-use, and no routing to alternatives despite numerous sibling calculators covering the same sub-tasks.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources