Skip to main content
Glama
Sign In
wealth-engine

wealth-engine

by Jaume9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

50/30/20 Budget Analyzer

budget_analyzer

Analyze your monthly budget against the 50/30/20 rule to identify overspending, unallocated money, and get recommendations to increase savings.

Instructions

Analyze a monthly budget against the 50/30/20 rule (needs/wants/savings). Surfaces overspending, unallocated money, your actual split vs the target, and concrete recommendations to raise your savings rate.

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": {
      "monthlyIncome": "<monthlyIncome>",
      "categories": "<categories>"
    },
    "name": "budget_analyzer"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoriesYesYour budget categories.
monthlyIncomeYesMonthly take-home income.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It transparently describes the tool as an analyzer that surfaces overspending and recommendations, implying read-only, non-destructive behavior. However, it does not explicitly state that no modifications occur or mention any side effects.

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

Conciseness5/5

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

Two sentences with no redundancy. The first sentence identifies the purpose and rule, the second lists actionable outputs. Perfectly front-loaded and efficient.

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 two parameters and no output schema, the description fully covers input requirements and expected results (overspending, unallocated money, split comparison, recommendations). No gaps remain.

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%, so baseline is 3. The description adds overall context (50/30/20 rule) but does not enhance understanding of individual parameters beyond the schema, which already describes them clearly.

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 clearly states it analyzes a monthly budget against the 50/30/20 rule, listing specific outputs like overspending and recommendations. This distinguishes it from sibling financial calculators such as debt_payoff or fire_calculator.

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?

The description implicitly indicates use for budget analysis but provides no explicit guidance on when to use this tool vs alternatives like side_hustle_ranker or subscription_audit. No when-not-to-use or context hints are given.

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

Deploy Server

Other Tools