Skip to main content
Glama

PoliErgaleio

plan_monthly_budget

Builds a monthly budget from a list of expenses at any frequency: normalises everything to a monthly basis, tiers each item (T1 fixed essentials, T2 variable essentials, T3 lifestyle, T4 discretionary), and returns cash-basis disposable income, savings rate after expenses and investments, the biggest optimisable leak and a surplus projection; deficit months clamp savings at zero. Use to summarize a household's actual monthly net income and expense items. Ask for the actual expense ledger or item amounts; never fabricate expenses. Entries without a frequency are treated as monthly and disclosed. Omitted investment contributions are treated as zero and disclosed.

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": {
      "monthlyNetIncome": "<monthlyNetIncome>",
      "expenses": "<expenses>"
    },
    "name": "plan_monthly_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
expensesYesExpense items. Known catalogue keys (mortgageRent, groceries, netflix, fuel, ...) are tiered automatically; otherwise pass an explicit tier.
projectionYearsNoHorizon of the surplus projection (default 10).
monthlyNetIncomeYesTake-home monthly income, EUR (net of tax, social insurance and GESY); zero is valid but savings rate is unavailable.
targetSavingsRateNoSavings-rate goal as a percent of net income.
monthlyInvestmentsNoRecurring monthly investments/savings, EUR.
expectedAnnualReturnNoAssumed annual return on invested surplus, percent (default 0).

Output Schema

NameRequiredDescriptionDefault
seriesNo
projectionYes
savingsGapYes
tierTotalsYes
assumptionsYes
largestLeakYes
savingsRateYes
annualExpensesYes
categoryTotalsYes
monthlySurplusYes
disposableIncomeYes
monthlyNetIncomeYes
targetSavingsRateYes
discretionaryTotalYes
monthlyInvestmentsYes
targetMonthlySavingsYes
totalMonthlyExpensesYes
currentMonthlySavingsYes
totalMonthlyOutgoingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / currentMonthlySavings
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / totalMonthlyOutgoings
      Added value: +{
      +  "type": "number"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "monthlyNetIncome",
      -  "totalMonthlyExpenses",
      -  "tierTotals",
      -  "categoryTotals",
      -  "monthlyInvestments",
      -  "disposableIncome",
      -  "monthlySurplus",
      -  "savingsRate",
      -  "annualExpenses",
      -  "largestLeak",
      -  "discretionaryTotal",
      -  "targetSavingsRate",
      -  "targetMonthlySavings",
      -  "savingsGap",
      -  "projection",
      -  "assumptions"
      -]New value: +[
      +  "monthlyNetIncome",
      +  "totalMonthlyExpenses",
      +  "totalMonthlyOutgoings",
      +  "tierTotals",
      +  "categoryTotals",
      +  "monthlyInvestments",
      +  "disposableIncome",
      +  "monthlySurplus",
      +  "currentMonthlySavings",
      +  "savingsRate",
      +  "annualExpenses",
      +  "largestLeak",
      +  "discretionaryTotal",
      +  "targetSavingsRate",
      +  "targetMonthlySavings",
      +  "savingsGap",
      +  "projection",
      +  "assumptions"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations present, the description carries the full behavioral burden and does so richly: it discloses normalization to monthly, tier assignment, cash-basis disposable income, savings rate after expenses and investments, leak detection, surplus projection, and the deficit-month clamp at zero. It also states fallback behavior for missing frequency and omitted investments, including that these are disclosed.

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?

The description front-loads the core purpose and output behavior, then adds data-integrity guidance and default-handling notes. It is dense but appropriately sized for a multi-parameter calculation tool, though the long opening sentence could be split for easier scanning.

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

Completeness5/5

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

Given the complexity of a six-parameter budget calculator with a rich schema and an output schema, the description is complete enough to call correctly. It covers purpose, data requirements, normalization, tiering, outputs, defaults, and disclosure behavior.

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 parameter meanings are already well documented in the input schema. The description adds some useful semantic context, such as treating missing frequency as monthly and omitted investments as zero, but it does not materially extend most individual parameter definitions beyond the schema baseline.

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: it builds a monthly budget from expense items at any frequency. It also names the normalization, tiering, and output metrics, so an agent can distinguish this household-budget summarizer from sibling calculators such as retirement stress tests or mortgage simulations.

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?

It gives clear usage context: summarize a household's actual monthly net income and expense items, and ask for the actual ledger or item amounts rather than fabricating expenses. It does not explicitly name alternatives or when-not-to-use cases, so it falls short of the top score.

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