Skip to main content
Glama

Moedux — Diagnóstico Financeiro

prever_mar_vermelho

Apenas a data do Mar Vermelho (quando o saldo chega a zero) a partir de Saldo Inicial, Entrada mensal e Conta Fixa. Se quiser também o saldo projetado em um ano, use projetar_saldo_12_meses. Usa o mesmo motor de projeção do diagnóstico do Moedux e devolve 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": "prever_mar_vermelho"
  }
}

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

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose useful behavior beyond the parameters — the computation mirrors the Moedux diagnostic engine and the result is a link with values pre-filled — but it says nothing about the read-only/non-mutating nature, what happens when expenses exceed income (no zero crossing), or the date format returned.

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 short sentences, front-loaded with the output definition followed by the alternative and then the implementation note. Slightly padded by the 'same engine as the Moedux diagnostic' remark, which is context rather than instruction, but overall efficient.

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 simple three-parameter calculation with no output schema, the description covers what it computes, which sibling to use instead, and that the response is a link with prefilled values. The remaining gap is edge-case behavior (entrada <= saida, date format), which is minor but real given the absence of annotations and output schema.

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 saldo, entrada and saida with units and meaning. The description restates the same three concepts in prose without adding constraints or format details beyond what the schema provides; baseline 3 applies.

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 names a specific computed output — the 'Mar Vermelho' date, defined inline as the point where the balance reaches zero — and the three inputs it derives from (Saldo Inicial, Entrada mensal, Conta Fixa). It also explicitly separates itself from the sibling tool, so an agent can pick it without opening either schema.

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

Usage Guidelines5/5

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

It gives an explicit routing condition: if the caller also wants the projected balance a year out, use projetar_saldo_12_meses. The 'Apenas' (only) framing tells the agent this tool returns the zero-crossing date alone, which is the key distinction from the alternative.

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.