EveryCalc

calculate_inflation

Read-onlyIdempotent

What an amount in today's dollars will buy after a number of years at a given annual inflation rate, what today's basket will cost then, the cumulative price increase percent, and the purchasing power lost. Use when the user asks what money will be worth in the future, or what a future amount costs in today's dollars. For whether a raise keeps up use calculate_raise_vs_inflation. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive inflation calculator calculator.

Input Schema

Name	Required	Description
`years`	No	Years into the future.
`amount`	Yes	Amount in today's dollars.
`annual_rate_pct`	Yes	Annual inflation rate percent, e.g. 3.
`include_schedule`	No	Set to true to include the purchasing power schedule in 5 year steps (or about 6 steps for longer horizons), matching the page table.

Output Schema

Name	Required	Description
`ok`	Yes	True when the calculation succeeded.
`note`	Yes	Disclaimer that accompanies every result.
`tool`	Yes	Name of the tool that ran.
`inputs`	No	The normalized inputs the calculation used.
`results`	Yes	The computed figures for this calculator.
`calculator_url`	Yes	Deep link to the matching interactive calculator on everycalc.xyz.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026

addedOutput schema / properties / note

Added value: +{
+  "description": "Disclaimer that accompanies every result.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "ok",
-  "tool",
-  "results",
-  "calculator_url"
-]New value: +[
+  "ok",
+  "tool",
+  "results",
+  "calculator_url",
+  "note"
+]

Changed1 schema field changedOct 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "calculator_url": {
+      "description": "Deep link to the matching interactive calculator on everycalc.xyz.",
+      "type": "string"
+    },
+    "inputs": {
+      "description": "The normalized inputs the calculation used.",
+      "type": "object"
+    },
+    "ok": {
+      "description": "True when the calculation succeeded.",
+      "type": "boolean"
+    },
+    "results": {
+      "description": "The computed figures for this calculator.",
+      "type": "object"
+    },
+    "tool": {
+      "description": "Name of the tool that ran.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool",
+    "results",
+    "calculator_url"
+  ],
+  "type": "object"
+}

First observedOct 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds genuinely non-annotated behavior: the result carries a calculator_url that the agent is instructed to render as a clickable markdown link, which is an output-presentation obligation the schema cannot convey.

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 core purpose and the routing rule are front-loaded in efficient sentences. The final IMPORTANT directive is worth its length, though the duplicated phrase 'interactive inflation calculator calculator' is a sloppy artifact that slightly undercuts the polish.

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?

With an output schema present, the description need not restate return values, yet it usefully previews them and adds the critical calculator_url presentation requirement. For a read-only, idempotent calculator with full schema coverage, this is close to complete; only explicit handling of edge inputs (e.g. zero or fractional years) is absent.

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 all four parameters (years, amount, annual_rate_pct, include_schedule) are already documented with examples like 'e.g. 3'. The description only gestures at the inputs in prose without adding format, bounds, or default semantics beyond the schema, so the 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 verb-resource pair and enumerates the four concrete outputs (future purchasing power, future cost of today's basket, cumulative price increase percent, purchasing power lost). It also explicitly distinguishes itself from the sibling calculate_raise_vs_inflation, so an agent can disambiguate 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 Guidelines5/5

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

It states both directions of use ('what money will be worth in the future' and 'what a future amount costs in today's dollars') and routes the adjacent case ('whether a raise keeps up') to calculate_raise_vs_inflation by name. Nothing about when to pick this tool is left to inference.

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

All EveryCalc tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.