Skip to main content
Glama

EveryCalc

calculate_sgli_vs_private_insurance

Read-onlyIdempotent

Cost comparison of SGLI (0.06 USD per 1,000 USD of coverage per month plus a 1 USD monthly fee) against a private term premium over the given number of years: monthly and total SGLI cost, total private cost, and which is cheaper. The page's age field is not used by its calculation and is not a parameter here. Use when the user compares SGLI coverage cost with a private life insurance quote. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive SGLI vs private insurance calculator.

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": {
      "coverage": "<coverage>",
      "private_monthly": "<private_monthly>",
      "years": "<years>"
    },
    "name": "calculate_sgli_vs_private_insurance"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsYesComparison horizon in years (minimum 1, as on the page).
coverageYesLife insurance coverage amount in USD.
private_monthlyYesPrivate term insurance monthly premium in USD.

Output Schema

NameRequiredDescriptionDefault
okYesTrue when the calculation succeeded.
noteYesDisclaimer that accompanies every result.
toolYesName of the tool that ran.
inputsNoThe normalized inputs the calculation used.
resultsYesThe computed figures for this calculator.
calculator_urlYesDeep link to the matching interactive calculator on everycalc.xyz.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / note
      Added value: +{
      +  "description": "Disclaimer that accompanies every result.",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "ok",
      -  "tool",
      -  "results",
      -  "calculator_url"
      -]New value: +[
      +  "ok",
      +  "tool",
      +  "results",
      +  "calculator_url",
      +  "note"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "calculator_url": {
      +      "description": "Deep link to the matching interactive calculator on everycalc.xyz.",
      +      "type": "string"
      +    },
      +    "inputs": {
      +      "description": "The normalized inputs the calculation used.",
      +      "type": "object"
      +    },
      +    "ok": {
      +      "description": "True when the calculation succeeded.",
      +      "type": "boolean"
      +    },
      +    "results": {
      +      "description": "The computed figures for this calculator.",
      +      "type": "object"
      +    },
      +    "tool": {
      +      "description": "Name of the tool that ran.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "ok",
      +    "tool",
      +    "results",
      +    "calculator_url"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral value beyond that: the pricing model (0.06 USD per 1,000 USD of coverage per month plus a 1 USD monthly fee), the fact that all inputs are unit-bearing USD/years, and the mandatory calculator_url linking behavior.

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-loaded with the comparison and its outputs, then usage, then the output-handling instruction. The dense rate parenthetical is essential domain data rather than filler; no sentence is redundant.

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?

An output schema exists, yet the description still names the returned fields and adds the non-obvious requirement to render calculator_url as a markdown link — exactly the kind of post-call obligation structured fields cannot convey. Nothing needed to call it correctly is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description goes further by supplying the SGLI rate structure that gives 'coverage' and 'years' real computational meaning, and by explicitly ruling out an age parameter that sibling calculators might lead an agent to expect.

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 comparison ('SGLI vs private term premium') and enumerates exactly what is computed: monthly and total SGLI cost, total private cost, and the cheaper option. The formula constants and the note that the page's age field is intentionally excluded make it unmistakable among the many calculate_* siblings.

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?

'Use when the user compares SGLI coverage cost with a private life insurance quote' gives a clear triggering condition. It does not name alternatives or state when not to use it (e.g., comparing two private policies), so it stops short of full routing guidance.

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.