Skip to main content
Glama

CoverSavvy Term Life Insurance Rates

compare_terms

Given a fixed profile (age, gender, health class, coverage), returns rates across all available term lengths (10, 15, 20, 25, 30, 35, 40 years). Helps answer 'should I get a 20 or 30 year term?'

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": {
      "age": "<age>",
      "gender": "<gender>",
      "health_class": "<health_class>",
      "coverage": "<coverage>"
    },
    "name": "compare_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYesApplicant age (20–65)
genderYes
coverageYesCoverage amount in dollars (e.g. 500000 for $500K). Call list_options for valid values.
health_classYespreferred = best non-tobacco rate, standard = average non-tobacco rate, standard_tobacco = tobacco user rate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It implies a pure read/pricing lookup with no mutation, but it does not state whether rates are illustrative or binding, whether the call is rate-limited or cached, or what happens for profiles outside the supported range. For a read-only lookup tool this is adequate but not rich.

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?

Two sentences, front-loaded with the input contract and the return scope, with the motivating question as a closing hook. Nothing is redundant, though the parenthetical term-length enumeration borders on schema-level detail.

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

Completeness3/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 must explain returns, and it only says 'returns rates across all available term lengths' — it does not say whether rates are monthly or annual, in dollars, or in what structure they come back. Combined with zero annotations, an agent still has meaningful gaps about the response shape before calling.

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 75%, so the schema already documents age range, the health_class enum meanings, and the coverage unit. The description merely restates the four inputs as 'a fixed profile' without adding format, constraint, or interaction meaning. Baseline 3 is appropriate given the schema does the heavy lifting.

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 description gives a specific verb-and-resource statement: it takes a fixed profile (age, gender, health class, coverage) and returns rates across all available term lengths, enumerating them (10–40 years). That distinguishes it in substance from compare_health_classes (which varies health class) and query_rates, though it never names those siblings explicitly.

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 conveyed only implicitly through the example question 'should I get a 20 or 30 year term?', which does signal the comparison scenario. There is no explicit when-to-use versus when-to-use-a-sibling guidance, no stated prerequisites, and no exclusions (e.g., when to use query_rates instead).

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