Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goodrx_drugs

List GoodRx drugs by A-Z directory letter and return each drug's name, slug, GoodRx URL, and drug-information URL. Falls back to stale cached data if GoodRx is unreachable.

Instructions

List GoodRx drugs by letter. Lists the drugs GoodRx files under one letter of its A-Z directory, chosen with the required letter (a to z). Each drug has its name, price-page slug, GoodRx URL and drug-information URL. If GoodRx is unreachable, a retained copy up to about a day old is returned and flagged with an X-Availability-Mode: stale header.

Input Schema

NameRequiredDescriptionDefault
letterYesDirectory letter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses the response shape (name, slug, URLs) and a non-obvious fallback behavior (a retained ~1-day-old copy flagged with an X-Availability-Mode: stale header). It does not mention pagination, rate limits or auth, keeping it short of 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 compact sentences, front-loaded with the core action and scope, then the required parameter, then output/fallback detail. No filler sentences.

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 browse tool with no output schema and no annotations, the description covers purpose, parameter, returned fields and the stale-data behavior. The main remaining gap is lack of any alternative-tool routing, but the operational picture is essentially complete.

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 description coverage is 100% and the single parameter is an explicit a-z enum, so the schema already fully documents it. The description restates the letter range but adds no format or edge-case detail beyond the schema, which is the expected baseline.

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 GoodRx drugs') plus the exact scoping mechanism (the A-Z directory letter). It clearly distinguishes this browse-by-letter tool from siblings like goodrx_drug_prices or goodrx_drug_options that operate on specific drugs.

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 description makes the intended use (browsing the directory by letter) implicit through 'Lists the drugs GoodRx files under one letter of its A-Z directory', but never states when to prefer this over alternatives such as goodrx_brands, goodrx_classes or goodrx_drug_options, nor any exclusions.

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