Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

goodrx_answers

List GoodRx health questions with their slugs to access medication and health Q&A. Returns top questions and all questions grouped by drug.

Instructions

List GoodRx health questions. Returns GoodRx's medication and health questions: the index's top questions and every question with its slug, grouped by drug where GoodRx's index groups it (questions GoodRx lists only in its sitemap carry just their slug). Use a slug with /goodrx/answer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.6/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 full behavioral burden. It does disclose meaningful return-shape behavior: output is grouped by drug where the index groups it, and sitemap-only questions carry just a slug. It does not state whether results are paginated, sorted, or scoped, but for a static read-only list this is reasonable coverage.

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?

Two sentences, front-loaded with the core purpose before the return-shape detail. The middle parenthetical about sitemap-only questions is a bit dense but earns its place by explaining an otherwise confusing output quirk.

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?

With no output schema, the description must convey what comes back, and it does: top questions plus all questions with slugs, grouped by drug, with an explanation of the slug-only edge case. For a zero-parameter list tool with no annotations, this is close to complete, though ordering and volume are unstated.

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 to disambiguate and the baseline for an empty schema is 4. The description introduces the concept of question slugs (used by the sibling detail tool) but that is not a parameter here.

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?

"List GoodRx health questions" gives a specific verb and resource, and the description clarifies the scope (index top questions plus every question with slug, grouped by drug). It also points to the consuming pattern ("Use a slug with /goodrx/answer"), which implicitly distinguishes it from the singular goodrx_answer tool. It stops just short of naming the sibling tool directly.

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

Usage Guidelines3/5

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

The line "Use a slug with /goodrx/answer" tells the agent this is an index whose output feeds a detail lookup, which is useful routing context. There is no explicit statement of when not to use it or which of the many goodrx_* siblings to prefer, so usage is implied rather than stated.

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