Skip to main content
Glama

Get carrier market view

get_carrier
Read-onlyIdempotent

An insurance carrier's group business from Form 5500 filings: employers, premium, covered lives, lines, top states, brokers placing it, median comp rate, largest employers; plus its fully insured small- and large-group market share, 3-year MLR and rebates owed by state from CMS Medical Loss Ratio data (field mlr). Carriers with 5+ employers.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCarrier name or slug, e.g. Cigna

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With annotations already declaring readOnly, idempotent and non-destructive behavior, the description adds real substance: upstream sources (Form 5500 filings and CMS Medical Loss Ratio data), the `mlr` field label, and the 5+ employer inclusion threshold. It says nothing about what happens when a carrier name is unmatched or ambiguous, which matters for a lookup keyed on free-text name/slug.

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?

Every clause carries information - metrics, data sources, thresholds - with no filler, and the core purpose leads. Structure is the weak point: it is one long semicolon-and-parenthesis run-on that is harder to scan than a short lead sentence plus a field list.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with no output schema, the description effectively serves as the return-value spec by enumerating both the Form 5500 metrics and the CMS MLR fields. The main gap is failure behavior when the carrier is not found or is below the 5-employer threshold.

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 100% and the schema itself already explains 'Carrier name or slug, e.g. Cigna'. The description adds no matching rules, slug format, or ambiguity handling beyond that, so the baseline of 3 applies.

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 (a carrier's group business) and enumerates the exact contents: employers, premium, covered lives, lines, top states, brokers, median comp rate, market share, 3-year MLR and rebates. It clearly separates this carrier-centric view from employer-, broker- and state-centric siblings. It falls short of 5 only because the 'fetch one carrier's profile by name' framing is implied by the possessive rather than stated as a verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no alternative named; an agent must infer from sibling names which tool to pick. The only routing-style statement, 'Carriers with 5+ employers,' is a data-coverage threshold rather than a usage rule.

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