EveryCalc

calculate_brs_vs_high3

Read-onlyIdempotent

Pension-only comparison of the legacy High-3 system (2.5 percent per year of service) against the Blended Retirement System (2.0 percent per year) on the same high-3 average basic pay: monthly, annual, and 30-year lifetime differences. Excludes TSP matching, continuation pay, COLA, and taxes. Use when a service member compares the legacy High-3 pension with the Blended Retirement System pension. 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 BRS vs High-3 calculator.

Input Schema

Name	Required	Description	Default
`years_of_service`	Yes	Years of service, clamped by the page to 20 to 40.
`high3_monthly_avg`	Yes	High-3 average monthly basic pay in USD.

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.2/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the bar is lower. The description adds real value by disclosing scope limits (excludes TSP matching, continuation pay, COLA, taxes) and an output-handling requirement (surface calculator_url as a markdown link). It does not state precision/rounding assumptions, but the model's core limits are transparent.

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-loaded with the comparison and formula rates, then scope limits, then usage trigger, then the important output instruction. Dense but each sentence contributes; the ALL-CAPS directive is slightly heavy-handed but serves a concrete purpose.

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 an output schema present, return values need no explanation, and the description still summarizes the returned deltas (monthly, annual, 30-year lifetime). Purpose, scope exclusions, usage trigger, and the calculator_url handling requirement together cover everything an agent needs to call and present this tool correctly.

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% and both parameters are documented, including the 20–40 year clamping behavior, so the schema carries the load. The description adds the conceptual meaning of high-3 average pay ('on the same high-3 average basic pay') but no format or unit guidance beyond what the schema states (USD).

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 comparison (High-3 2.5%/yr vs BRS 2.0%/yr on the same high-3 average) and the outputs produced (monthly, annual, 30-year lifetime differences). The 'pension-only' qualifier plus the exclusion list separates it from siblings like calculate_military_retirement_pension and calculate_tsp.

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?

Gives an explicit trigger ('Use when a service member compares the legacy High-3 pension with the BRS pension') and the exclusions imply what it should not be used for (TSP matching, continuation pay → calculate_tsp). It stops short of naming the sibling tool to use instead, so it is clear context without explicit exclusions.

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.