Skip to main content
Glama

Check up to 100 provider and plan pairs

check_network_batch
Read-onlyIdempotent

The check_network answer for up to 100 (npi, plan_id) pairs in one request, with the same listed / listed_in_named_network / contracted_network / not_found / no_provider_network semantics. Invalid pairs come back with a per-item error and are not charged; each accepted pair costs 1 call. Needs the Builder plan or higher.

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": {
      "items": "<items>"
    },
    "name": "check_network_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoDefault plan year for items that do not set one. Optional.
itemsYes1 to 100 pairs.

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.5/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, and the description adds genuinely new behavior: invalid pairs return per-item errors rather than failing the call, invalid pairs are not charged, and each accepted pair consumes 1 call. The Builder-plan requirement adds an auth/tier constraint not present in 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence pack, front-loaded with what the tool returns, followed by the enumeration semantics, the error/billing behavior, and the tier requirement. Every clause carries information an agent would otherwise have to guess.

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?

Output schema exists, so return shape needn't be explained, yet the description still names the outcome enum values and the per-item error case. With 2 parameters at full schema coverage, tier gating, and billing semantics all covered, nothing an agent needs to call it correctly is missing.

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 the schema already documents npi, plan_id and the year default behavior in detail. The description reinforces the (npi, plan_id) pairing and the 100-item ceiling but adds no syntax or format detail beyond the schema, so this sits at the baseline.

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 (check network) and resource, plus the batching scope ('up to 100 (npi, plan_id) pairs in one request'). It explicitly frames itself as the batch form of the sibling 'check_network', so an agent can tell the two apart without opening either schema.

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 batch-vs-single routing against check_network is clear from 'The check_network answer for up to 100 pairs', and the 'Needs the Builder plan or higher' prerequisite is a real usage gate. It stops short of an explicit 'use check_network for one pair' exclusion, but the context is unambiguous.

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