Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

healthgrades_hospital

Retrieve a Healthgrades hospital profile with awards, clinical outcome ratings, patient-experience measures, address, and phone. Use it to evaluate hospital quality without patient reviews.

Instructions

Get a Healthgrades hospital profile. Returns one Healthgrades hospital profile: hospital-wide and specialty awards with years, clinical outcome ratings by service line (procedure or condition, measure, outcome rating, and 1-5 stars), patient-experience measures with national comparisons, address, and phone. Patient-authored reviews are not returned. Requests use US egress because Healthgrades restricts content by region.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesHealthgrades hospital profile URL from /healthgrades/facilities/search

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: the tool uses US egress due to regional restrictions, and it excludes patient-authored reviews. However, it does not mention rate limits, caching, authentication requirements, or whether the operation is read-only (though 'Get' implies a read).

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?

The description is compact and front-loaded: the first sentence states the purpose, followed by details of the return data and constraints. It is efficient and every sentence adds value, though it could be slightly more structured with bullet points for the returned fields.

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?

Given that there is no output schema and only one parameter, the description must explain the return values. It does so comprehensively, listing the types of data returned and explicitly noting exclusions. The addition of the US egress constraint completes the operational picture. Minor gap: it does not clarify if the URL must be exact or if variations are accepted.

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%, so the single parameter 'url' is fully documented in the schema, including its origin. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 ('Get') and resource ('Healthgrades hospital profile'), and the description enumerates exactly what the profile contains. This distinguishes it from siblings like healthgrades_physician and healthgrades_facility, which cover different entity types.

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 description implies usage by specifying the input is a profile URL from /healthgrades/facilities/search, and notes patient reviews are not returned, which implicitly guides the user to another tool for reviews. However, it does not explicitly state when to use this versus healthgrades_facility or healthgrades_physician, nor does it mention prerequisites or alternatives.

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