Skip to main content
Glama
Sign In
retirement-contribution-limits-2027-mcp

retirement-contribution-limits-2027-mcp

by theluckystrike
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Social Security COLA, wage base and earnings test

get_social_security_cola
Read-onlyIdempotent

Retrieve official Social Security COLA and related 2025–2027 figures, including taxable maximum, earnings test limits, and SSI amounts, by calendar year.

Instructions

Returns the Social Security cost-of-living adjustment and related figures from SSA's official annual notice in the Federal Register: 2027 COLA 3.6% (announced October 2026), 2027 taxable maximum (wage base) $192,300, retirement earnings test limits ($25,560 under full retirement age, $67,920 in the year you reach it, for 2027), quarter of coverage, SGA amounts and SSI federal payment. Covers 2025, 2026 and 2027.

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": {
      "year": "<year>"
    },
    "name": "get_social_security_cola"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesCalendar year: 2025, 2026 or 2027.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description goes beyond them by naming the provenance (SSA's official annual notice in the Federal Register) and by disclosing a concrete figure set, which tells the agent this is authoritative published data rather than a computed estimate.

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?

One front-loaded sentence opens with the verb and the subject, then enumerates the returned figures. The dense numeric listing is long but each figure earns its place as expected return content, though it risks going stale and could have been condensed into field names.

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 return content and does so by listing the concrete returned figures. Combined with annotations covering the safety profile and a fully documented single parameter, an agent has everything needed to invoke it 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 description coverage is 100% and the single parameter already documents the valid range (2025-2027) with min/max bounds. The description restates the same year coverage without adding format or semantics beyond the schema, 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?

The definition states a specific verb ('Returns') and a well-defined resource set (COLA, taxable maximum, earnings test limits, quarter of coverage, SGA, SSI), so the agent knows exactly what data comes back. It does not explicitly contrast itself with the sibling tools (get_contribution_limits, compare_years), leaving the differentiation to be inferred from content rather than stated.

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: the year range ('Covers 2025, 2026 and 2027') signals when it is applicable, but there is no explicit statement of when to call this instead of get_contribution_limits or compare_years. 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.

Deploy Server

Other Tools