Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

healthgrades_health_topics

Fetch Healthgrades Health A-Z topics (conditions, body systems, treatments, wellness, drugs) with article counts, last-modified dates, and hub URLs.

Instructions

List Healthgrades Health A-Z topics. Returns every topic of Healthgrades' Health A-Z library (conditions, body systems, treatments, and wellness topics) with its article count, last-modified date, and topic hub URL where one exists, plus the drugs topic for Healthgrades' drug articles. Use a slug with /healthgrades/health-articles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.2/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 disclosure burden. It usefully describes the return shape (article count, last-modified date, hub URL) which is valuable since no output schema exists, but it says nothing about pagination, ordering, or rate limits for a full-library listing.

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 verb+resource, then the payload detail, then the follow-on pointer. Efficient overall, though the second sentence packs return fields and the drugs-topic caveat densely enough that it borders on a run-on.

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 zero-parameter, read-only listing tool with no annotations and no output schema, the description adequately covers what is returned and how the result chains into the articles endpoint. Nothing an agent needs to call it 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?

The tool takes zero parameters, so there is nothing for the description to clarify beyond the schema. Baseline 4 applies; the enumerations of topic categories add mild context but no parameter detail is possible.

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 (List) and resource (Healthgrades Health A-Z topics), then enumerates the exact lines included (conditions, body systems, treatments, wellness, plus the drugs topic). The trailing pointer to /healthgrades/health-articles distinguishes it from the sibling article tool.

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?

The final sentence signals the follow-on step ('Use a slug with /healthgrades/health-articles'), which implicitly tells the agent this is the discovery/enumeration entry point before fetching articles. There is no explicit when-not-to-use or comparison to goodrx_health_topics, so it falls short of a 5.

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