Skip to main content
Glama

get_insurance_benchmark

Read-only

Insurance financial performance benchmarks — combined ratio, loss ratio, expense ratio, and reserve adequacy by line of business. Source: NAIC annual statistical report. For insurance CFOs, actuaries, and analysts reviewing underwriting performance. $0.02 USDC per call.

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": {
      "line_of_business": "<line_of_business>"
    },
    "name": "get_insurance_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_sizeNo
line_of_businessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description only needs to add context. It does so meaningfully by disclosing the data source (NAIC annual statistical report) and the per-call cost ($0.02 USDC), both of which affect an agent's decision to call. It omits data vintage/freshness, which matters given an annual source.

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?

Four short front-loaded clauses: metrics first, source second, audience third, price last. No filler, though the fragment style is terse enough that some connective clarity is lost.

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?

For a read-only benchmark lookup with no output schema and only two enum parameters, the essentials are present. However, it never says what the response looks like, whether results are segmented by company_size, or how current the annual NAIC data is — gaps an agent would need to interpret results.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, but it only partially does: 'by line of business' maps to line_of_business, while company_size is never mentioned and its segmentation effect on results is unexplained. The enum values are self-describing, which limits the damage, but half the parameters get no semantic support.

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 names the resource precisely (insurance financial performance benchmarks) and enumerates the metrics returned — combined ratio, loss ratio, expense ratio, reserve adequacy — plus the NAIC source, which separates it from the other sector-benchmark siblings. It stops short of naming a specific alternative, but the domain naming does the disambiguation work.

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 audience line ('For insurance CFOs, actuaries, and analysts reviewing underwriting performance') implies the usage context, but there is no explicit when-to-use vs when-not-to-use guidance and no prerequisites or exclusions stated.

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