Skip to main content
Glama
Sign In

mcp

by io.seaworthy
OverviewDiscussionsAdmin

estimate_benefit_cap_gap

Read-only

Compute the income replacement gap between a group long-term disability benefit cap and a target replacement of earned income. Pure math, no external calls. Unauthenticated.

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": {
      "annual_income": "<annual_income>",
      "group_monthly_cap": "<group_monthly_cap>"
    },
    "name": "estimate_benefit_cap_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
annual_incomeYesGross earned income in US dollars.
benefit_taxableNoWhether group benefits would be taxable (true if employer pays premiums). Default true.
group_monthly_capYesGroup LTD policy monthly benefit cap in US dollars.
marginal_tax_rateNoCombined federal + state marginal rate as a decimal. Default 0.35.
group_replacement_percentNoHeadline group replacement percent. Default 0.60.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, and the description is consistent with them. It adds genuinely new behavioral context beyond the annotations by disclosing that the computation is pure math with no external calls and requires no authentication.

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?

Three short sentences with zero filler, front-loading the computation before the operational notes. Every sentence earns its place.

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 five-parameter math tool with full schema coverage and safety annotations, the description covers purpose and operating conditions adequately. With no output schema, it could say a bit more about the shape of the returned gap, but 'compute the income replacement gap' gives the agent a reasonable expectation.

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%, so all five parameters (including defaults for benefit_taxable, marginal_tax_rate, and group_replacement_percent) are already documented in the schema. The description reuses the terms 'benefit cap' and 'earned income' but adds no syntax, format, or default information beyond what the schema provides, so the baseline of 3 applies.

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 ('Compute') and a precise resource ('income replacement gap between a group LTD benefit cap and a target replacement of earned income'). The 'pure math, no external calls' clause also implicitly separates it from sibling tools like quote_request or submit_estimate_request.

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?

The description implies usage context by noting it is a pure-math, unauthenticated calculation, which tells the agent it needs no account or external setup. However, it never states when to prefer this over alternatives such as estimate_premium_range or price_configuration, leaving routing to inference.

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

All mcp toolsInspect
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