Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goodrx_drug_guide

Fetch a GoodRx drug guide for a specific drug and topic—side effects, dosage, or interactions—to get frequencies, prices, and severity-grouped interactions.

Instructions

Get a GoodRx drug guide. Returns one dedicated GoodRx drug guide. side-effects: common and less common side effects with reported frequencies, serious and reported side effects, and the label source. dosage: coupon price per dosage and quantity for each dosage form, and typical dosing. interactions: interacting drugs grouped by severity (not_recommended, usually_not_recommended, increased_risk), with GoodRx slugs where linked. Includes reviewer, last-reviewed date, and related guides. Use pairs from /goodrx/drug-guides; a drug without that guide returns 404. Requests use US egress because GoodRx is US-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesDrug slug from /goodrx/drug-guides
topicYesGuide topic

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does meaningful work: it discloses that a drug lacking the guide yields 404 and that requests require US egress because GoodRx is US-only. It does not cover authentication or rate limits, but the content-per-topic breakdown and error semantics are genuinely additive.

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?

The purpose and input sourcing are front-loaded, and the per-topic detail earns its space by telling the agent what it gets back. The opening two sentences ('Get a GoodRx drug guide. Returns one dedicated GoodRx drug guide.') are redundant, which is the only real waste.

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 must describe the return payload and it does so thoroughly per topic, including reviewer, last-reviewed date, and related guides. Combined with input sourcing, the 404 case, and the US-egress constraint, nothing material is missing for a 2-param tool.

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 schema already documents both parameters and the enum; the baseline would be 3. The description goes beyond the terse 'Guide topic' label by spelling out what each of side-effects, dosage, and interactions actually returns, adding real semantic meaning to the enum choices.

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 ('Get a GoodRx drug guide') and enumerates the three guide topics it can return, so an agent knows exactly what it fetches. It also implicitly separates itself from the goodrx_drug_guides listing by pointing at that endpoint as the source of slug/topic pairs.

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?

Tells the agent to source the slug/topic pair from /goodrx/drug-guides and warns that an unsupported pair returns 404, which is real routing guidance. It stops short of explicitly contrasting itself with goodrx_drug_info or goodrx_drug_options, so the 'when not to use' side is left implicit.

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