Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

healthgrades_facilities_search

Search Healthgrades for hospitals, pharmacies, group practices, or urgent care near a US location. Get facility names, addresses, phones, distances, ratings, and available filters as clean JSON.

Instructions

Search Healthgrades hospitals, pharmacies, group practices, and urgent care. Returns one page of Healthgrades facility search results near a location for one facility type (hospital, pharmacy, group practice, or urgent care), with name, address, phone, distance, profile URL, affiliated provider and rating counts, hospital awards, and the filters available for the search. Requests use US egress because Healthgrades restricts content by region.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoResult page (1-500, 20 results per page)
sortNoResult order; patientsatisfaction is hospital-only and group_practice supports only distance
typeYesFacility type
awardNoHospital award value from /healthgrades/facilities/filters (type=hospital only)
queryNoOptional facility name or keyword
whereYesCity and state, or ZIP code
ratingNoHospital specialty-rating value from /healthgrades/facilities/filters (type=hospital only)
distanceNoSearch radius in miles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does reasonably well: it discloses pagination behavior ('one page'), enumerates the returned fields, and adds a genuinely useful operational constraint ('Requests use US egress because Healthgrades restricts content by region'). It omits auth/rate-limit details but is solid for a read-only search.

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?

Three sentences, front-loaded with the core purpose. The middle sentence is dense (long field enumeration) but informative rather than wasteful, and the region constraint is given its own closing sentence.

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?

No output schema exists, so the description must cover return values, which it does by listing result fields. Combined with the region/egress note and pagination behavior, it is complete enough for an agent to call the tool correctly, with only minor gaps around result limits and filter acquisition.

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%, so the schema already documents every parameter including enum constraints and the hospital-only restriction on award/rating. The description adds no parameter-level syntax or format detail beyond what the schema provides, making the baseline 3 appropriate.

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?

The description opens with a specific verb+resource ('Search Healthgrades hospitals, pharmacies, group practices, and urgent care') and clarifies the scope is one facility type at a time near a location. It distinguishes itself from a single-facility lookup, but never names its siblings (e.g., healthgrades_facility or healthgrades_facilities_filters), so the agent must infer the boundary from context.

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 implied: it is a paginated search returning results 'near a location.' The constraint that only one facility type can be queried per request is stated implicitly via the parenthetical list, but there is no explicit when-to-use / when-not-to-use guidance or routing to the filters or facility-detail siblings.

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