Skip to main content
Glama

Search doctors and hospitals by name

search_providers
Read-onlyIdempotent

Searches OpenHealth's public records for a doctor or hospital by name. Returns up to 10 matches with the doctor's NPI or the hospital's CCN, the city, the state and the OpenHealth page. A hospital search needs a two-letter state. A doctor search can be narrowed by state. When no doctor has the exact name, it returns doctors with similar names and marks them.

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

Input Schema

NameRequiredDescriptionDefault
kindNodoctor or hospital. The default is doctor.doctor
nameYesThe doctor's or hospital's name, such as Matthew Bernhard or Riverside Methodist.
stateNoA two-letter US state code, such as OH.

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
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description usefully adds the 10-result cap and the fuzzy-match fallback behavior ('returns doctors with similar names and marks them'), which is genuine behavioral disclosure beyond the annotations; it still omits anything about ranking, truncation beyond the cap, or empty-result handling.

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?

Three short sentences, no filler, front-loaded with the action and result shape before the parameter conditions. Every sentence carries distinct information.

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 and rich annotations already present, the description only needs to fill behavioral gaps, which it mostly does via the result cap, returned identifiers, and fuzzy-match marking. Remaining gaps (no mention of empty-result behavior, ranking order, or what 'marks them' looks like in the response) are minor.

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 a baseline of 3 applies, but the description adds conditional semantics the schema cannot express: state is effectively required when kind is hospital and optional when kind is doctor. That is meaningful meaning beyond the flat string/pattern definitions.

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 ('Searches OpenHealth's public records for a doctor or hospital by name') and defines the scope as name-based lookup, which separates it in practice from NPI-based lookups like get_doctor. It stops short of naming any sibling tool explicitly, so differentiation has to be inferred.

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?

Gives real preconditions: a hospital search requires a two-letter state, while a doctor search can optionally be narrowed by state. That is clear operational guidance, but it never says when to choose this over get_doctor or get_hospital, so there are no explicit alternatives or exclusions.

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