Skip to main content
Glama

Plans that list a provider

plans_for_provider
Read-onlyIdempotent

Every Marketplace (ACA) and Medicare Advantage plan whose network directory lists the provider, one row per plan and plan year, each with plan name, insurer, state, network tier, evidence_tier (the row's answer, highest tier first), source {type, as_of} and evidence (every proof we hold for that plan, in tier order). Rows with evidence_tier 'named_network' are plans whose own name identifies their network, where the insurer's directory lists the provider in that network (network_name); report them as 'listed in the network this plan names', never as 'listed'. Rows with evidence_tier 'contracted_network' are plans where the insurer's published contract files list this provider in the network for the plan's product (network_labels); report them as 'contracted network', never as 'listed'. Medicare Advantage rows carry service_area_states and provider_state_in_service_area. Filter by market, state or year; page with limit and offset (next_offset is null on the last page). A plan missing from this list is not a statement that the provider is out of network. Costs 1 call per page.

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

Input Schema

NameRequiredDescriptionDefault
npiYes10-digit National Provider Identifier, as a string, e.g. "1184617268".
yearNoPlan year, e.g. 2026. Optional; by default all plan years we hold are considered.
limitNoPlans per page, 1 to 500. Default 50.
stateNo2-letter US state code, e.g. "OH". Optional.
marketNo"aca" = Marketplace plans, "ma" = Medicare Advantage plans. Optional; default both.
offsetNoRows to skip; pass next_offset from the previous page. Default 0.

Output Schema

NameRequiredDescriptionDefault
dataYesThe answer. Same shape as the matching InPlan API v1 endpoint.
notesNoHow to read the answer.
sourcesYesSource types behind the answer (insurer_directory, plan_directory, provider_registry, plan_catalog), each with its as_of date.
data_as_ofYesDate (YYYY-MM-DD) of the newest data behind this answer.
request_idYesRequest id; quote it when you contact support.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, closed-world and non-destructive behavior, and the description adds material cost ('Costs 1 call per page'), pagination termination ('next_offset is null on the last page'), and mandatory reporting rules per evidence_tier. The negative-result caveat and the never-say-'listed' constraints are behavioral guidance found nowhere in the structured fields.

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?

Front-loaded with the core scope, then the tier semantics, then filters and paging cost — a sensible order with no filler sentences. It is compressed into one very long block, which makes the reporting rules harder to scan than a short bulleted list would.

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

Completeness5/5

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

For a paginated, evidence-attributed lookup with a rich output schema, the description covers what rows mean, how tiers must be phrased, what extra MA fields appear, paging, and interpretation of absence. An agent could call and report results correctly without further context.

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?

Schema coverage is 100%, so the schema already defines all six parameters and the market enum. The description still adds value by explaining the offset/next_offset round-trip and framing year/state/market as filters over retained plan years, which goes slightly beyond the field-level text.

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 precise resource and direction — every ACA and MA plan whose network directory lists the provider, one row per plan-year — which unambiguously separates it from the reverse-direction sibling search_plan_providers. It never names a sibling explicitly, so the differentiation is implied by scope rather than stated.

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

Usage Guidelines4/5

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

Gives concrete filtering and paging guidance ('Filter by market, state or year; page with limit and offset') and a valuable interpretive caveat: 'A plan missing from this list is not a statement that the provider is out of network.' It stops short of explicitly routing the agent to check_network or search_plan_providers for the opposite question.

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