Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

healthgrades_physician

Fetch a doctor's public Healthgrades profile to retrieve professional details and practice locations for credentialing or contact research.

Instructions

Get a Healthgrades physician profile. Returns public professional profile fields and practice locations for one Healthgrades physician. Patient-authored review text is not returned. Requests use US egress because Healthgrades restricts some content by region.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical Healthgrades physician profile URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does useful work: it discloses that patient-authored review text is deliberately omitted (an important boundary on what the agent will and won't get) and that requests route through US egress due to regional content restrictions. It does not discuss rate limits or error behavior, but the return-content and egress disclosures are substantive beyond the schema.

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?

Four tight sentences, each front-loaded and earning its place: purpose, return contents, explicit exclusion, and egress behavior. No redundancy or 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 no output schema, the description compensates by describing the returned fields (public professional profile plus practice locations) and by excluding review text. For a single-parameter fetch tool this is nearly complete; only pagination/error behavior and profile-completeness caveats are absent.

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% for the single url parameter, so the schema already documents it as the constant "canonical Healthgrades physician profile URL." The description adds no format, validation, or derivation guidance beyond what the schema states, so the baseline 3 applies.

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 ("Get a Healthgrades physician profile") and scopes it to "one Healthgrades physician," which implicitly distinguishes it from the paged healthgrades_physicians_search. It stops short of explicitly naming the sibling search tool, so the agent must infer that this is the URL-based single-record lookup.

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?

The one-URL-per-physician framing implies this is a lookup-by-URL tool rather than a discovery tool, but there is no explicit when-to-use guidance or pointer to healthgrades_physicians_search for finding a physician you lack a URL for. Usage is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools