Skip to main content
Glama

Is this provider in this plan?

check_network
Read-onlyIdempotent

Answers whether one plan's network directory lists one provider. answer "listed" (in_network: true) comes with evidence: plan year, network tier and source {type, as_of}. answer "not_found" (in_network: null) means no listing was found in current directory data for this provider and plan; it is NOT a statement that the provider is out of network, so never report it as "out of network". answer "listed_in_named_network" (in_network: null) means the plan's own name identifies its network and the insurer's directory lists the provider in that network; evidence carries network_name and as_of; report it as "listed in the network this plan names", never as "listed". answer "contracted_network" (in_network: null) means the insurer's published contract files list this provider in the network for this plan's product; the evidence item with evidence_tier "contracted_network" carries network_labels and as_of; report it as "contracted network", never as "listed". When a directory listing also exists, the answer is "listed" and the contracted item follows it in evidence. answer "no_provider_network" is a drug-only plan. Directories change; tell users to confirm with the plan before care. 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": {
      "npi": "<npi>",
      "plan_id": "<plan_id>"
    },
    "name": "check_network"
  }
}

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.
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

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, but the description adds substantial behavior context beyond them: what evidence accompanies each answer type (plan year, network tier, source type/as_of, network_name, network_labels), the precedence rule when both directory and contract listings exist, and the staleness caveat. That is real value for an agent composing a response.

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 purpose is front-loaded in sentence one and every subsequent sentence carries semantic weight about an answer value. It is, however, a dense block of long multi-clause sentences with repeated 'never as listed' phrasing that could be tighter as a list.

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?

With an output schema present, return structure need not be described, and annotations cover the safety profile. The description still supplies the full answer-taxonomy semantics and the evidence fields per answer, which is exactly what an agent needs to call this correctly and report results without misleading users.

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%, so npi, plan_id, and year are already fully documented in the schema, including the year defaulting behavior. The description adds no parameter-level detail beyond implying a single plan/provider pair, so the baseline 3 applies.

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?

The first sentence states a precise verb and resource: it answers whether one plan's network directory lists one provider. The exhaustive enumeration of answer values (listed, not_found, listed_in_named_network, contracted_network, no_provider_network) makes the tool's scope unmistakable and distinct from the sibling tools like coverage or lookup_provider.

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?

The description gives strong interpretation guidance: not_found is not proof of out-of-network, how to phrase each answer for users, and to advise confirming with the plan. It does not, however, say when to prefer this over siblings such as check_network_batch or coverage, so tool selection is left partly to inference.

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