Skip to main content
Glama

Get a doctor's public record

get_doctor
Read-onlyIdempotent

Gets one doctor's public record by 10-digit NPI. The record includes offices, specialties, doctor ratings for each scored procedure with the reasons, affiliated hospitals, federal exclusion list checks, and published procedure counts and outcome measures with their sources. A rating describes predicted results at the doctor's affiliated hospitals. OpenHealth gives no overall doctor score.

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

Input Schema

NameRequiredDescriptionDefault
npiYesThe doctor's 10-digit National Provider Identifier (NPI).

Output Schema

NameRequiredDescriptionDefault
dataNo
notesNo
statusYes
sourcesNo
page_urlNo
release_idNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

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, closed-world, non-destructive behavior, and the description adds real semantics beyond them: what the record contains, that ratings are procedure-level and reflect predicted results at affiliated hospitals, and that no overall score exists. It does not mention auth needs or data freshness, so it stops short of a 5.

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 purpose, then contents, then two clarifications about rating semantics. The contents enumeration is long and partly duplicates the output schema, but each clause is informative and 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?

For a single-parameter read tool with an output schema and complete annotations, this is nearly complete; the rating-semantics and 'no overall score' notes preempt likely misinterpretation. The main missing piece is routing guidance relative to the search siblings.

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 coverage is 100% and the single NPI parameter is fully documented with its pattern, so the schema does the heavy lifting. The description's 'by 10-digit NPI' is consistent but adds no meaning beyond the schema.

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 ('Gets one doctor's public record') and pins the retrieval key ('by 10-digit NPI'), which separates it from the search/find siblings that locate doctors rather than fetch a single record. The scope of the record is enumerated, so an agent knows what it is retrieving.

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?

Usage is only implied: the requirement for a 10-digit NPI signals the tool is for looking up a known doctor, but the description never says when to use it instead of search_providers, find_doctors_for_procedure, or check_doctor_insurance, nor does it say to search first if only a name is known.

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