Skip to main content
Glama

CoverSavvy Term Life Insurance Rates

query_rates

Returns the monthly and annual premium for a specific profile. All 5 parameters are required.

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>",
      "term": "<term>"
    },
    "name": "query_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYesApplicant age (20–65)
termYesTerm length in years: 10, 15, 20, 25, 30, 35, or 40
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. Changed1 schema field changed
    • changedInput schema / properties / term / description
      Previous value: -"Term length in years: 10, 15, 20, 25, or 30"New value: +"Term length in years: 10, 15, 20, 25, 30, 35, or 40"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the return payload (monthly and annual premium), which is valuable with no output schema, but says nothing about whether the operation is read-only/no-side-effect, how out-of-range or invalid combinations are handled, or rate/quoting caveats.

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?

Two short sentences, front-loaded with the purpose and followed by the required-input constraint. No filler, no repetition, nothing to trim.

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 annotations and no output schema, the description should carry more of the behavioral load; it does name the returned values but omits error behavior and whether the call is a pure read. Combined with well-described schema parameters (80% coverage), it is adequate but leaves gaps for a 5-required-parameter pricing tool.

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 80%, and the schema already documents age range, term values, coverage units, and health_class meanings. The description's 'All 5 parameters are required' merely restates the schema's required array, adding no new meaning about parameter interactions or pricing implications.

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 states a concrete operation (returns monthly and annual premium) against a specific resource (a profile defined by 5 parameters), which is more precise than the bare name 'query_rates'. It does not explicitly contrast itself with siblings compare_health_classes and compare_terms, so an agent must infer that this fetches a single quote rather than a comparison.

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 only implied: the phrase 'for a specific set of parameters' suggests single-configuration pricing in contrast to the comparison siblings, and 'All 5 parameters are required' gives a call-shape constraint. There is no explicit when-to-use / when-not-to-use guidance, and no mention of list_options for discovering valid coverage values (though the schema's coverage field does reference it).

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