Skip to main content
Glama

Stratalize Intelligence

Get Insurance Benchmark

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds two genuinely useful behavioral facts not in structured fields: the upstream source (NAIC annual statistical report) and a metered price of $0.02 USDC per call, which lets an agent reason about cost before invoking. It says nothing about the response shape, granularity (annual?), or latency, so the addition is real but thin.

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?

Three compact fragments, front-loaded with the resource, then metrics, then source/audience/price. No filler or repetition. Slightly clipped to the point of omitting the parameter explanation, but nothing is wasted.

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 does well to enumerate the metrics that come back, and the NAIC source grounds the data. However, a two-parameter, no-output-schema lookup tool needs at least a note on what company_size changes and what a result record contains; that omission leaves an agent able to call it but unsure of the comparison basis.

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% across 2 parameters, so the description must carry the meaning and largely does not. 'By line of business' hints at the role of line_of_business, but neither it nor company_size (small/mid_size/large) is explained, and the effect of company_size on the returned benchmark is unstated. Enum values are legible but the semantics of segmenting by size are left to guesswork.

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?

States a specific resource (insurance financial performance benchmarks) and enumerates the metrics returned: combined ratio, loss ratio, expense ratio, reserve adequacy, by line of business. The insurance domain in the name and text clearly separates it from the other benchmark siblings (agricultural, bank regulatory, cap rate, etc.), though it never names an alternative tool.

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?

'For insurance CFOs, actuaries, and analysts reviewing underwriting performance' gives audience and an implied context of use, but there is no explicit when-to-use vs when-not, no prerequisites, and no routing to a relevant sibling for adjacent questions (e.g., other regulatory benchmarks). Usage is inferred rather than 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