Skip to main content
Glama

Glacier Planner: Free Canadian Retirement Calculator

Calculate a first Canadian retirement plan

calculate_retirement
Read-onlyIdempotent

Use the person’s supplied numbers to calculate whether savings cover spending and compare one explicit alternative: retirement age, household spending, or CPP/QPP and OAS start ages. A benefit-age comparison keeps the supplied amount at 65 and residence years fixed. It is not a search for a better start age. Free, no sign-in. Returns annual results, assumptions, provenance and a portable input artifact; no saved-record lookup or mutation.

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": {
      "input": "<input>"
    },
    "name": "calculate_retirement"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / input / properties / alternative / properties / cppStartAges
      Added value: +{
      +  "description": "One explicit CPP or QPP start age per person. The amount at 65 stays as supplied. Quebec below 65 is rejected. Not a search for a better age.",
      +  "items": {
      +    "maximum": 70,
      +    "minimum": 60,
      +    "type": "integer"
      +  },
      +  "maxItems": 2,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • addedInput schema / properties / input / properties / alternative / properties / oasStartAges
      Added value: +{
      +  "description": "One explicit OAS start age per person. Residence years stay as supplied. Not a search for a better age.",
      +  "items": {
      +    "maximum": 70,
      +    "minimum": 65,
      +    "type": "integer"
      +  },
      +  "maxItems": 2,
      +  "minItems": 1,
      +  "type": "array"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior. The description adds useful context beyond them: free access with no sign-in, the exact output contents (annual results, assumptions, provenance, portable input artifact), and the rule that benefit-age comparisons keep the amount at 65 and residence years fixed.

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?

Front-loads purpose, then narrows the alternative behavior and explicitly rules out search, then adds access and output information. Every sentence adds distinct information and there is no redundant restatement of the tool name or title.

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?

For a complex first-calculation tool with a rich nested schema and no output schema, the description covers purpose, alternatives, output contents, and the absence of saved-record operations. It could say more about required assumption acceptance and input prerequisites, but the schema already documents those nested requirements.

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?

The top-level input parameter has 0% schema description coverage, so the description must carry more weight. It does clarify the semantics of the alternative object—one explicit alternative, with benefit-age comparisons holding the supplied amount and residence years fixed—but it does not explain the many nested input fields; that burden remains on the schema's nested descriptions.

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 verb and resource: calculate whether savings cover spending and compare one explicit alternative among retirement age, household spending, or CPP/QPP and OAS start ages. It also distinguishes itself from an optimizer by saying it is "not a search for a better start age." An agent can tell exactly what this tool does and what it does not do.

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?

Makes the intended context clear: use the person's supplied numbers for a first Canadian retirement calculation and compare one explicit alternative. It explicitly excludes saved-record lookup, mutation, and benefit-age optimization, but does not spell out prerequisites such as the required assumptions confirmation beyond what the schema enforces.

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