Skip to main content
Glama

Get state market view

get_state
Read-onlyIdempotent

Employee benefits market in one state: employers, participants, premium, funding mix, top medical carriers, top brokers, renewal months, median comp rate, largest employers; plus fully insured small- and large-group market share, 3-year MLR and rebates owed by carrier from CMS Medical Loss Ratio data (field mlr), which also covers groups too small to file a 5500.

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

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter state code, e.g. OH

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare the operation read-only, idempotent, closed-world, and non-destructive. The description adds substantive context beyond annotations by stating the CMS Medical Loss Ratio provenance and noting that mlr covers groups too small to file a 5500.

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?

The description is one front-loaded sentence that moves from scope to returned data without boilerplate. It is dense with field names, but those details are useful because the tool has no output schema.

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?

With no output schema, the description appropriately enumerates the major data categories returned and notes the CMS MLR caveat. It stops short of explaining units, metric definitions, or data vintage, but it is complete enough for correct selection and invocation.

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?

There is only one parameter, and schema coverage is 100%; the schema already documents it as a two-letter state code. The description adds no additional parameter semantics, 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 a specific resource and scope: employee benefits market data for one state, with an enumerated set of returned dimensions. It is clear what the tool does, though it does not explicitly distinguish itself from get_benchmarks or the entity-level sibling tools.

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 explicit when-to-use guidance, prerequisites, or comparison to alternatives. An agent must infer from the state-level market scope that this is for aggregate market views rather than employer, broker, or carrier lookups.

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