Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goodrx_health_topics

List GoodRx Health article topics by section and topic with article counts and last-modified dates; filter by section to browse conditions, drugs, insurance, or well-being.

Instructions

List GoodRx Health article topics. Returns every GoodRx Health article topic as section and topic pairs with article counts and last-modified dates, optionally for one section. Sections: conditions, health-topic, well-being, pet-health, insurance, classes, drugs, healthcare-access, corporate, hcp (clinician resources), and drug (articles about one drug; the topic is the drug slug). Use the pairs with /goodrx/health-articles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionNoArticle section

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 full behavioral burden, and it does disclose a lot: the return contents (section/topic pairs, counts, last-modified dates), the optional scoping, and special semantics for 'drug' and 'hcp'. 'List' implies a read-only, non-destructive operation. It omits any note on pagination/result size, which keeps it from a 5.

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 purpose and return shape, then the section enumeration, then the integration hint. The section list is long but mostly necessary, and the two annotated values (hcp, drug) justify its presence rather than duplicating the enum idly.

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 and no annotations, yet the description compensates by describing the returned structure and scoping behavior in the text. For a single optional-enum-parameter listing tool, nothing an agent needs in order 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% and the enum is present, so the baseline is 3, but the description adds meaning beyond the enum list by explaining 'hcp (clinician resources)' and 'drug (articles about one drug; the topic is the drug slug)'. It also clarifies the parameter is an optional single-section filter.

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?

The opening states a specific verb and resource ('List GoodRx Health article topics') and immediately describes the exact output shape (section/topic pairs with article counts and last-modified dates). The topic-taxonomy scope is specific enough that an agent can tell it apart from the sibling article-fetching tools (goodrx_health_articles, goodrx_health_article) without opening a schema.

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 description gives clear usage context: the section filter is optional, and it routes the agent downstream with 'Use the pairs with /goodrx/health-articles.' That is real workflow guidance. It stops short of stating when NOT to use it or naming explicit alternatives, so it does not reach 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