Skip to main content
Glama

Check a doctor's insurance plan listings

check_doctor_insurance
Read-onlyIdempotent

Checks which insurance plan directories list a doctor, by NPI or by name with an optional state, and optionally for one insurer such as Aetna, Cigna or Medicare. Returns each listing with its plans, its update date and whether the directory lists the doctor as accepting new patients, plus Medicare and Medicaid billing. No listing means unknown, not out of network. A listing does not confirm coverage. Only the plan can confirm it.

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": "check_doctor_insurance"
  }
}

Input Schema

NameRequiredDescriptionDefault
npiNoThe doctor's 10-digit National Provider Identifier (NPI).
stateNoA two-letter US state code, such as OH.
insurerNoOne insurer to check, using one of the listed ids, such as aetna or medicare.
doctor_nameNoThe doctor's full name, such as Matthew Bernhard. Use it when you have no NPI.

Output Schema

NameRequiredDescriptionDefault
dataNo
notesNo
statusYes
sourcesNo
page_urlNo
release_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the bar is lower, yet the description adds real interpretive value: 'No listing means unknown, not out of network' and 'A listing does not confirm coverage. Only the plan can confirm it.' Those caveats prevent a wrong downstream conclusion and are not in any structured field.

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 action and lookup modes, then three short sentences of caveats; every sentence carries information. The opening sentence is long and could be split, but nothing is filler.

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 0 required params, an output schema, and full annotation coverage, the description supplies what structure cannot: the rule that at least one identifier is expected and that absence of a listing is not a negative result. What remains thin is explicit routing to sibling lookup tools.

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 baseline is 3, but the description adds meaning the schema does not: it ties 'state' to the name-based path ('by name with an optional state'), implying the dependency between doctor_name and state that the flat schema leaves unstated, and confirms the insurer filter takes a single value.

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 specific verb and resource: 'Checks which insurance plan directories list a doctor,' with the two lookup modes (NPI, or name plus optional state) and the optional single-insurer filter. This clearly separates it from profile-style siblings like get_doctor, though no sibling is named explicitly.

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?

'by NPI or by name with an optional state' implies which input path to use, but there is no explicit when-to-use versus get_doctor or search_providers, and no statement of prerequisites or when not to call it. Usage is inferable rather than prescribed.

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