Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goodrx_drug_options

List a GoodRx drug's prescription options by slug, including every brand and generic label, dosage form, strength, quantity, and default prescription for drug price lookups.

Instructions

List a GoodRx drug's prescription options. Returns every brand and generic label, dosage form, strength, and quantity GoodRx prices for one drug, with GoodRx's default prescription. Use these values for /goodrx/drug-prices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesDrug slug from /goodrx/drugs

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 exist, so the description carries the full behavioral burden. It does describe the returned fields (labels, forms, strengths, quantities, default prescription), which is meaningful, but says nothing about permissions, rate limits, or caching/freshness traits. Adequate but incomplete for a tool with zero annotation 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?

Three sentences, front-loaded with the core action, then the output contents, then the downstream routing. No filler, though the return-field enumeration is slightly dense.

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 read tool with no output schema and no annotations, the description covers what the tool does, what it returns, the param source, and where to use the result. Only the absence of behavioral details (auth, limits) keeps it from a 5.

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% (the single slug param is documented as coming from /goodrx/drugs), so the baseline is 3. The description reinforces that the slug maps to 'one drug' but adds no format or syntax detail beyond the schema.

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?

The description leads with a specific verb and resource ('List a GoodRx drug's prescription options') and enumerates exactly what the payload contains (brand/generic label, dosage form, strength, quantity). It is clearly distinguishable from complement tools like goodrx_drug_prices by its framing as the options source, though it does not explicitly contrast with goodrx_drug_info or goodrx_drug_guide.

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?

It gives clear context for downstream use ('Use these values for /goodrx/drug-prices'), effectively telling the agent this tool precedes pricing lookups, and the schema names the slug's origin (/goodrx/drugs). There is no explicit when-not-to-use guidance, so it stops 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