Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

healthgrades_health_articles

List paginated Health A-Z articles for a health topic, returning slug, URL, and last-modified date with total pages. Set topic=drugs for drug articles.

Instructions

List Healthgrades Health A-Z articles in a topic. Returns one page of a Healthgrades Health A-Z topic's articles (slug, URL, and last-modified date), most recently modified first, with total and total pages. Use topic=drugs for drug articles. Use an article URL with /healthgrades/health-article.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, starting at 1
topicYesTopic slug from /healthgrades/health-topics
page_sizeNoArticles per page (1-200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.5/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 and does well: it discloses pagination ('one page'), ordering ('most recently modified first'), and the returned aggregate fields ('total and total pages'). It does not mention auth or rate-limit 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.

Conciseness5/5

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

Three sentences, front-loaded with the operation and its pagination semantics, then the usage hints. Every sentence adds information with no filler.

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?

There is no output schema, so the description appropriately enumerates the return fields (slug, URL, last-modified date, total, total pages) and the pagination model. 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%, so the baseline is 3, but the description adds meaning beyond the schema by specifying the special value topic=drugs for drug articles, which is not encoded anywhere in the schema (no enums). It still doesn't clarify page_size bounds (1-200 is only in the schema).

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 and resource ('List Healthgrades Health A-Z articles in a topic') and scopes the result to one page of a topic's articles. It also implicitly distinguishes itself from the singular sibling healthgrades_health_article by pointing at '/healthgrades/health-article'.

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?

Gives concrete usage hints: 'Use topic=drugs for drug articles' and routes article-URL lookups to the sibling tool. It provides context but no explicit when-not to use this tool beyond that routing note.

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