Skip to main content
Glama

Plan details

get_plan
Read-onlyIdempotent

Details of one Marketplace (ACA) or Medicare Advantage plan by plan ID: name, insurer or organization, state or service area, plan type, metal level, the plan years we hold, and whether we hold its directory listings, with their as_of date. For some plans sold only outside the marketplace, contracted_network {labels, as_of}: the network labels of the insurer's published contract files for the plan's product. Costs 1 call.

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

Input Schema

NameRequiredDescriptionDefault
yearNoPlan year, e.g. 2026. Optional; by default all plan years we hold are considered.
plan_idYesPlan ID. Marketplace (ACA) plans: 14 characters like "29276OH0970001" (a 16-character "-01" variant form is accepted). Medicare Advantage plans: "H1234-001-000" (the segment "-000" is optional).

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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond them: it flags the explicit cost ("Costs 1 call") and discloses that contracted_network is only present for some off-marketplace plans, including its as_of semantics — non-obvious conditional behavior an agent should anticipate.

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?

Two sentences, front-loaded with the identity and purpose before the field inventory and the conditional contracted_network caveat. The field list is dense but every item maps to real returned data; slightly run-on phrasing keeps it from a 5.

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 an output schema present, the description need not detail return values, yet it still previews them and explains the conditional contracted_network block and as_of date. Only the lack of guidance about when to prefer batch/network siblings leaves a small gap.

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%, including the plan ID format variants and the year default, so the schema does the heavy lifting. The description restates the plan-ID-based lookup but adds no syntax or filtering nuance beyond it, making the baseline 3 appropriate.

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

Purpose5/5

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

States a specific verb and resource ("Details of one ... plan by plan ID") and then enumerates exactly what comes back: name, insurer, state/service area, plan type, metal level, plan years, directory listings. It also disambiguates the two plan universes (Marketplace ACA vs Medicare Advantage) and the conditional contracted_network block, which clearly separates it from network/coverage/provider siblings.

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?

The phrase "one ... plan by plan ID" implies this is the single-plan lookup versus broader siblings like check_network_batch or plans_for_provider, and "Costs 1 call" hints at cost tradeoffs. But no alternative is named and no when-not condition is given, so routing must be inferred from the sibling names.

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