Skip to main content
Glama

BreastPump.com Coverage Navigator

Get a state's rules

get_state_rules
Read-onlyIdempotent

A summary of coverage for every plan type in one state, with its Medicaid program link.

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_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes2-letter code or name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds that the payload is an aggregate covering every plan type plus a Medicaid program link, which is useful behavioral context, but it says nothing about what happens with an unknown state or how results are framed.

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?

One compact sentence with no filler, and the return content is front-loaded. It could be tightened by leading with a verb and reconciling the 'rules' framing.

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 single-parameter read-only tool with full schema coverage and no output schema, the description conveys enough to call it, but it omits the response shape and error behavior, and leaves the 'rules' vs 'coverage summary' relationship unexplained.

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 single 'state' parameter is documented as '2-letter code or name', so the schema does the work. The description adds no further meaning about accepted formats or scoping.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the return content — a per-plan-type coverage summary for a single state plus a Medicaid program link — but never names the action (get/retrieve) and never mentions 'rules' despite the tool name and title 'Get a state's rules', leaving a gap between the name and what is described. An agent can guess the resource, but the mismatch with the title creates ambiguity.

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 guidance on when to use this tool versus the sibling check_coverage or list_states, and no stated preconditions. The reader must infer that this is the state-level overview and check_coverage is the targeted lookup.

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