Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

healthgrades_hospital_awards

Retrieve Healthgrades hospital award recipients by award, year, state, city, or specialty to get profile URLs, addresses, phone numbers, and award years.

Instructions

List Healthgrades hospital award recipients. Returns one page (20 hospitals) of a Healthgrades hospital quality award list: America's Best Hospitals (top 50, 100, or 250), Specialty Excellence (by specialty, top 50 or 100), Patient Safety Excellence, Outstanding Patient Experience, Ob-Gyn Care, or Specialty State Rankings. Filter by year, state, city, specialty, and Ob-Gyn award type; sort by name or, with latitude and longitude, by distance. Each hospital includes its profile URL (for /healthgrades/hospital), address, coordinates, phone, and every award it holds with years. Read accepted filter values from /healthgrades/hospital-awards/filters. Requests use US egress because Healthgrades restricts content by region.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity slug from the filters for the state (requires state)
listNoAmerica's Best Hospitals list size (award=americas-best-hospitals)
pageNoPage number (20 hospitals per page)
sortNoResult order; distance requires latitude and longitude
yearNoAward year from the filters (defaults to the latest)
awardYesAward list
stateNoState slug from the filters
latitudeNoLatitude for distance sorting
longitudeNoLongitude for distance sorting
specialtyNoSpecialty code (award=specialty-excellence-americas-best-care or state-rankings)
ob_gyn_typeNoOb-Gyn award (award=ob-gyn-care-excellence-awards): GYS gynecologic surgery, LAB labor and delivery, OBG obstetrics and gynecology
list_categoryNoSpecialty Excellence list size (award=specialty-excellence-americas-best-care)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries full burden and delivers real behavioral context: 20-item pagination, the required US egress due to regional content restrictions, and the concrete fields returned (profile URL, address, coordinates, phone, awards with years). It stops short of rate-limit or error behavior, but covers the operationally important traits.

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?

Content is front-loaded: purpose and pagination first, then filters/sort, then return shape and the egress caveat. It is dense but every sentence maps to a distinct decision an agent must make; minor redundancy with the schema is the only drag.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter, no-output-schema tool it is complete: it explains pagination, filtering dimensions, sort prerequisites, the return payload, and the region-based egress constraint. Nothing an agent needs to invoke it correctly is missing.

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% and six parameters carry enums, so the schema already documents each field's meaning and constraints. The description mostly restates those relationships (e.g., list size for Americas Best, specialty for Specialty Excellence) rather than adding new syntax or semantics. Baseline 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?

Opens with a specific verb+resource ('List Healthgrades hospital award recipients') and immediately enumerates the distinct award lists covered. An agent can tell this apart from the sibling healthgrades_hospital_award_filters (which supplies accepted values) and healthgrades_hospital (profile lookup) without opening schemas.

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?

States explicit usage context — filter by year/state/city/specialty/Ob-Gyn type, sort by name or distance with lat/long — and routes the agent to /healthgrades/hospital-awards/filters for accepted values. It lacks an explicit 'when-not-to-use' or a named alternative tool, but the prerequisite direction is clear.

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