Skip to main content
Glama

get_fire

Calculates the years to financial independence (4% rule) from expenses, savings, return and age.

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": {
      "monthlyExpenses": "<monthlyExpenses>",
      "monthlyInvestment": "<monthlyInvestment>"
    },
    "name": "get_fire"
  }
}

Input Schema

NameRequiredDescriptionDefault
inflationNoAnnual inflation in % (default 3)
currentAgeNoCurrent age (default 30)
annualReturnNoExpected annual return in % (default 7)
monthlyExpensesYesMonthly expenses
currentPortfolioNoCurrent net worth (default 0)
monthlyInvestmentYesMonthly savings/investment

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A3.5/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 the core method (4% rule), which is genuine behavioral context for a projection, but it says nothing about assumptions, edge-case behavior (e.g. expenses exceeding savings so FI is never reached), or whether negative returns are handled. Being a pure side-effect-free calculation lowers the stakes, but the disclosure is still thin.

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?

One sentence, zero filler, and the calculation method is front-loaded before the input list. Nothing in it is redundant with the schema or padded.

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

Completeness3/5

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

With six parameters, no annotations, and no output schema, the description should describe what is actually returned (a single years value? a projection schedule? null when FI is unreachable?). It implies 'years' but leaves the return contract and the effect of optional params like inflation and currentPortfolio unaddressed.

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 all six parameters including defaults and ranges, making 3 the baseline. The description names four of the six inputs (expenses, savings, return, age) but adds no interpretation beyond the schema and omits inflation and current portfolio entirely.

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

Purpose4/5

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

States a specific verb ('Calculates') and resource ('years to financial independence (4% rule)'), which unambiguously identifies this as the planning calculator among a sibling set of crypto data fetchers. The tool name 'get_fire' alone would be opaque, but the description resolves it. It lacks an explicit contrast with the nearest siblings (get_portfolio_score, get_metrics), so it falls short of a 5.

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?

Usage is only implied: an agent infers this is the tool for retirement-timeline questions because the purpose is self-evident. There is no statement of when to prefer it over get_portfolio_score or get_metrics, and no prerequisites or exclusions are given.

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