Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goodrx_drug_info

Retrieve GoodRx drug pages as structured sections covering uses, side effects, dosage, interactions, warnings, and alternatives; supports people and pets for veterinary dosing.

Instructions

Get GoodRx drug information. Returns a drug's GoodRx information page as titled sections (uses, side effects, pros and cons, pharmacist tips, risks and warnings, dosage, interactions, contraindications, alternatives, pill images, references, and common questions), plus authors, publish and review dates, FAQs, and comparison links to alternatives. With audience=pets it returns the drug's cat and dog page (veterinary uses, side effects, and dosing) for drugs listed by /goodrx/pet-medications; other drugs return 404. Requests use US egress because GoodRx is US-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesDrug slug from /goodrx/drugs (or /goodrx/pet-medications for audience=pets)
audienceNopeople for the general page, pets for the cat and dog page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden well: it names the returned content shape (titled sections, authors, dates, FAQs, comparison links), discloses the 404 outcome for non-pet drugs under audience=pets, and flags that requests use US egress because GoodRx is US-only. It omits auth/rate-limit details, but the read-only nature and edge cases are otherwise disclosed.

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?

Front-loaded with purpose, then return contents, then the pets special case, then the egress constraint. The long parenthetical section list is dense but each element is informative; slightly verbose but no sentence is wasted.

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?

With no output schema, the description fully covers the return payload, the parameter-driven branch and its failure mode, and an operational constraint (US egress). Nothing an agent needs 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%, so baseline is 3, but the description adds real meaning beyond the schema: it identifies where the slug originates and clarifies the enums' behavioral consequences (pets selects the cat/dog page, which returns 404 for drugs not listed by /goodrx/pet-medications).

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 (Get) and resource (GoodRx drug information) and enumerates the returned sections, making it clearly distinct from siblings like goodrx_drugs (listing) or goodrx_pet_medications. An agent can tell what this returns without opening the schema.

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?

It implies the slug must come from /goodrx/drugs (or /goodrx/pet-medications for audience=pets) and describes the pets branch returning a 404 otherwise, which is useful precondition context. However it never explicitly states when to pick this over sibling drug tools or the reverse routing, leaving selection mostly to inference.

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