FreeDailyPro Calculators

converters_social_security

Read-onlyIdempotent

Social Security retirement benefit estimate with 2026 bend points

Input Schema

Name	Required	Description
`claimAge`	No	Age you start benefits, 62 to 70 (decimals such as 62.5 are rounded to whole months). Default 67.
`birthYear`	No	Birth year, which sets full retirement age (67 if born 1960 or later). Default 1960.
`yearsWorked`	No	With annualEarnings: years of work, up to 35 (default 35).
`annualEarnings`	No	Alternative to AIME: current yearly earnings (capped at the 2026 wage base of $184,500). AIME is estimated from it.
`averageIndexedMonthlyEarnings`	No	Your AIME (average indexed monthly earnings) from your SSA statement. Send this or annualEarnings.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 30, 2026

addedInput schema / properties / annualEarnings

Added value: +{
+  "description": "Alternative to AIME: current yearly earnings (capped at the 2026 wage base of $184,500). AIME is estimated from it.",
+  "type": "number"
+}

addedInput schema / properties / averageIndexedMonthlyEarnings / description

Added value: +"Your AIME (average indexed monthly earnings) from your SSA statement. Send this or annualEarnings."

addedInput schema / properties / birthYear

Added value: +{
+  "description": "Birth year, which sets full retirement age (67 if born 1960 or later). Default 1960.",
+  "type": "number"
+}

addedInput schema / properties / claimAge / description

Added value: +"Age you start benefits, 62 to 70 (decimals such as 62.5 are rounded to whole months). Default 67."

addedInput schema / properties / yearsWorked

Added value: +{
+  "description": "With annualEarnings: years of work, up to 35 (default 35).",
+  "type": "number"
+}

removedInput schema / required

Removed value: -[
-  "averageIndexedMonthlyEarnings"
-]

First observedOct 24, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is fully covered. The description adds only the '2026 bend points' detail — useful for knowing it uses current SSA formula constants — but says nothing about assumptions, which inputs are required vs alternative, or what the estimate returns.

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?

A single compact phrase with no filler and the key qualifier (2026 bend points) front-loaded. Efficient, though the brevity edges toward under-specification rather than polished concision.

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?

All five parameters are optional with rich schema docs, and no output schema exists — so the description should at least hint at what the estimate returns (monthly benefit amount, at what claim age). That gap leaves it merely adequate for an agent that needs to interpret results.

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%, including the AIME-vs-annualEarnings exclusivity and defaults, so the schema does the heavy lifting. The description adds no parameter meaning beyond the '2026 bend points' note, so baseline 3 applies.

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?

Names a specific calculation and resource: 'Social Security retirement benefit estimate'. It is clearly distinguishable from the many other converters_* financial tools (401k, 529, RMD) by resource. It stops short of stating scope or method, so it stops at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, no alternatives named. With well over a hundred siblings, an agent gets no help deciding between this and converters_401k or converters_rmd beyond the name itself.

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

All FreeDailyPro Calculators 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.

Resources

Need Help?