Skip to main content
Glama

Moedux — Diagnóstico Financeiro

projetar_saldo_12_meses

Use quando precisar do saldo projetado em 12 meses, não apenas da data do Mar Vermelho. Projeta o saldo em 12 meses e informa a data de risco a partir de Saldo Inicial, Entrada mensal e Conta Fixa, com o mesmo motor de projeção do diagnóstico do Moedux. Devolve o saldo projetado, o risco e um link com os valores já preenchidos.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "saldo": "<saldo>",
      "entrada": "<entrada>",
      "saida": "<saida>"
    },
    "name": "projetar_saldo_12_meses"
  }
}

Input Schema

NameRequiredDescriptionDefault
saidaYesConta Fixa mensal em reais
saldoYesSaldo Inicial em reais
entradaYesEntrada mensal recorrente em reais

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does well on outputs — projected balance, risk date, and a pre-filled link — and notes the projection engine matches the Moedux diagnostic, but it never says whether generating the link persists anything or is purely read-only, which matters for a tool that returns a shareable link.

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

Conciseness4/5

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

Three sentences, front-loaded with the use case and the sibling contrast, then computation, then outputs. There is minor redundancy between 'saldo projetado em 12 meses' in sentence one and 'Projeta o saldo em 12 meses' in sentence two, but nothing is wasted overall.

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?

With three required parameters, no annotations, and no output schema, the description covers the needed ground by explaining what is returned. The remaining gap is the nature of the generated link (ephemeral vs persisted), which is the one thing an agent could still get wrong.

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 coverage is 100% with all three parameters documented including units ('em reais'), so the schema already does the heavy lifting. The description restates the same concepts (Saldo Inicial, Entrada mensal, Conta Fixa) without adding range, rounding, or recurrence semantics beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Projeta o saldo em 12 meses e informa a data de risco') and explicitly distinguishes it from the sibling output ('não apenas da data do Mar Vermelho'). It also names the three inputs driving the calculation, so an agent can tell exactly what this tool produces.

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

Usage Guidelines4/5

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

The opening clause gives a clear when-to-use condition ('Use quando precisar do saldo projetado em 12 meses') and contrasts it with the Red Sea date projection. It stops short of naming and routing to the sibling tool directly, so the exclusion is implied rather than explicit.

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.