Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

healthgrades_facility

Look up a Healthgrades pharmacy, urgent care, or group practice profile by URL to retrieve hours, services, providers, locations, and nearby options.

Instructions

Get a Healthgrades pharmacy, urgent care, or group practice profile. Returns one Healthgrades pharmacy, urgent care center, or group practice profile; the type (pharmacy, urgent_care, or group_practice) is inferred from the URL. Pharmacies: opening hours, services (for example compounding, immunizations, Medicare), and nearby pharmacies. Urgent care centers: opening hours and aggregated visitor answers to amenity questions. Group practices: specialties, providers with specialty and rating, medical services offered, language services, office locations with phones and coordinates, FAQs, and nearby offices. All types include name, 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 pharmacy, urgent care, or group practice profile URL from /healthgrades/facilities/search

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 burden well: it discloses that the profile type is inferred from the URL, that patient-authored reviews are NOT returned, and that requests use US egress due to Healthgrades regional content restrictions. These are non-obvious operational traits 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then a well-organized per-type breakdown of return fields. Slight redundancy between the opening sentence and the 'Returns one...' sentence, but each sentence otherwise earns its place.

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?

With no output schema, the description fully compensates by enumerating return contents for all three types plus shared fields, and by flagging the reviews exclusion and region constraint. Nothing an agent needs to call it correctly is missing.

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% (one url param, fully described), so baseline is 3. The description adds meaning beyond the schema by explaining that the facility type is inferred from the URL, informing how that single parameter drives the returned shape.

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 ('Get') and resource ('Healthgrades pharmacy, urgent care, or group practice profile'), then enumerates exactly what each of the three facility types returns. An agent can tell it apart from hospital/physician siblings by the named types, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never says when to use this tool versus the many siblings (healthgrades_facilities_search, healthgrades_physicians_search, healthgrades_hospital). It implies a URL-driven lookup but provides no prerequisite flow (e.g., 'first obtain the URL from healthgrades_facilities_search').

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