Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

healthgrades_autocomplete

Generate autocomplete suggestions for provider, specialty, condition, and procedure searches, returning structured JSON for free-text queries.

Instructions

Get Healthgrades search suggestions. Returns dynamic provider, specialty, condition, procedure, and other suggestions for a free-text query. Group categories vary with the query and are returned as data, not accepted as a closed enum.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesFree-text provider, specialty, condition, or procedure query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses that group categories vary per query and are returned as data rather than a fixed enum, which is real output-shape context. It says nothing about rate limits, auth, or result caps, but for a suggest endpoint that is a modest gap.

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 short sentences, front-loaded with the core purpose and followed by the useful dynamic-category caveat. Little waste, though the middle sentence is a partial restatement of the first.

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?

For a one-parameter, no-output-schema suggest tool, the description covers purpose, output content, and the non-enum behavior of the returned groups. Annotations are absent but the tool is low-risk and self-contained; only call-time limits are unaddressed.

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% with a single documented 'term' parameter, so the schema already explains the input. The description's restatement of the free-text domains (provider, specialty, condition, procedure) adds slight corroboration but no syntax or format detail beyond the schema. 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 Healthgrades search suggestions') and names what the output contains (provider, specialty, condition, procedure). It is clear enough to distinguish from a full search tool, though it doesn't explicitly contrast itself with siblings like healthgrades_physicians_search.

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?

No when-to-use or when-not-to-use guidance is given. The description implies it is for free-text autocomplete, but it never says to prefer this over healthgrades_specialties or healthgrades_physicians_search, nor does it mention that you might chain it into a 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