Skip to main content
Glama

BreastPump.com Coverage Navigator

List states

list_states
Read-onlyIdempotent

All 51 jurisdictions (50 states and DC), whether each has a verified state Medicaid rule, and the all-payer referral restriction flag.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_states"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the scope of the result set (fixed at 51 jurisdictions) and what each entry carries — the two flags. It does not disclose ordering or whether the flags can be null/unknown, which is the remaining behavioral gap.

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?

A single dense sentence with the scope front-loaded and no filler. It is a noun phrase rather than a verb-led statement, which slightly weakens the opening but costs nothing in length.

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?

There is no output schema, so the description carries the burden of describing the return shape; it names the two per-state fields but not their field names, types, or the record envelope. For a simple zero-parameter listing tool this is close to adequate, but the meaning of 'all-payer referral restriction flag' is left undefined.

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

Parameters4/5

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

The tool takes no parameters, so there is no parameter semantics to explain; the baseline applies. The description correctly signals that no filtering input is expected by framing the call as returning the complete jurisdiction set.

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: all 51 jurisdictions (50 states plus DC), and specifies the per-state payload — a verified-Medicaid-rule flag and an all-payer referral restriction flag. An agent knows exactly what comes back. It stops short of differentiating itself from the sibling get_state_rules, which presumably drills into per-state detail.

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?

Usage is only implied: it reads as a discovery/index listing, which makes the intent reasonably obvious for a zero-parameter tool. There is no explicit 'use this first, then call get_state_rules for the full rule text' routing, and no stated exclusions.

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