Numeratica — financial planning calculations

retirement_qlac

Retirement qlac. Numeratica POST /v1/retirement/qlac — returns JSON with result_id, engine_version, and a not-advice disclaimer (seed echoed for reproducible Monte Carlo where applicable). See the input schema for the accepted fields.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "retirement_qlac"
  }
}

Input Schema

Name	Required	Description	Default
`age`	No
`sex`	No
`tax_year`	No
`start_age`	No
`birth_year`	No
`assumed_rate`	No
`qlac_premium`	No
`account_balance`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 27, 2026

TDQS

D1.9/5.0

Behavior3/5

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

No annotations are present, so the description carries the full burden. It discloses the HTTP method (POST), response structure (result_id, engine_version, disclaimer), and Monte Carlo reproducibility (seed echoed). However, it omits side effects, permissions, or error behavior, and the Monte Carlo detail is vague.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short (1.5 sentences) and front-loaded with the tool name and endpoint. However, it includes a vague phrase 'where applicable' and omits critical information, making it thin rather than efficiently concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 undocumented parameters, no output schema, and a large sibling list, the description is severely incomplete. It does not explain the tool's function, parameter roles, or output interpretation, making it insufficient for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description only says 'See the input schema for the accepted fields.' It adds no meaning to any of the 8 parameters (age, sex, tax_year, etc.), failing to compensate for the schema's lack of descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Retirement qlac' and the endpoint, but lacks a specific verb or clear action. It does not explain what the tool computes or returns beyond generic fields, failing to distinguish it from numerous sibling retirement tools like 'retirement_monte_carlo' or 'annuity'.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of use cases, prerequisites, or exclusions, leaving the agent without any context for tool selection among many sibling tools.

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

All Numeratica — financial planning calculations 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.