Skip to main content
Glama

Senaro Personal Finance

by ai.senaro
OverviewDiscussionsAdmin

Emergency Fund Calculator

calculate_emergency_fund
Read-onlyIdempotent

Calculation, not advice. Verify with a professional before acting. Size an emergency fund target based on the borrower's monthly essential expenses, job stability, dependents, and income redundancy. Returns a tier breakdown (minimum, target, conservative; the target row is omitted when it equals the 3-month minimum, and the conservative row is omitted when it equals the 12-month ceiling), the gap between current savings and the target, and time-to-target at the supplied monthly savings cadence. Pairs with debt-payoff content for the recurring 'save vs pay debt' question.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolArgumentsYesJSON object with these parameters: monthly_essential_expenses: decimal > 0 (REQUIRED). Rent/mortgage + utilities + food + insurance + minimum debt payments. NOT discretionary spending. current_savings: decimal >= 0 (optional, default 0). What you have in liquid emergency-accessible savings today. job_stability: 'stable_w2' | 'variable_income' | 'self_employed' | 'between_jobs' (optional, default 'stable_w2'). Drives the target-months multiplier. stable_w2: salaried W-2 with consistent paycheck (+0 months). variable_income: W-2 with commission/bonus/shift-based pay (+1 month). self_employed: 1099 contractor / freelancer / sole proprietor (+3 months). between_jobs: actively job hunting, no current paycheck (+5 months). dependents: int >= 0 (optional, default 0). +1 target month per dependent, capped at +3. has_dual_income: bool (optional, default false). When true, partner income reduces the buffer by 1 month. monthly_savings_capacity: decimal >= 0 (optional, default 0). What you can contribute toward the gap each month. Drives months_to_target. Target months are clamped to [3, 12]: never below the 3-month personal-finance minimum, never above 12 (excess cash is better invested than parked). chart_title: string (optional) override for the chart title. Must not contain em-dashes or en-dashes. Max 120 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description goes further by disclosing the disclaimer/advice caveat, the exact tier structure with its row-omission rules, the clamping to [3,12] months, and what the gap and time-to-target outputs represent. This is rich behavior beyond what structured fields provide.

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?

Front-loads the disclaimer, then the purpose, then the return shape in fluid sentences. Slightly dense and leads with a caveat rather than the action, but every sentence earns its place with no filler.

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?

With no output schema, the description carries the full burden of describing returns and does so completely – tier breakdown, omission rules, savings gap, and time-to-target. An agent has everything needed to call and interpret the result.

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 effectively 100% – the nested toolArguments field fully documents each parameter, enumerates job_stability values, and states the clamping rule. The description adds conceptual framing (tiers, gap, time-to-target) but no syntax or defaults beyond the schema, so baseline 3 is appropriate.

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?

States a specific verb (size) and resource (emergency fund target) with the exact inputs that drive it: essential expenses, job stability, dependents, income redundancy. An agent can distinguish this from siblings like calculate_runway or payoff_vs_invest without opening the schema.

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?

Provides contextual pairing guidance ('pairs with debt-payoff content for the recurring save vs pay debt question') but never states when to use this tool versus alternatives such as calculate_runway or payoff_vs_invest, nor any exclusions. Usage is implied rather than directed.

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

All Senaro Personal Finance toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources