Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goodrx_drug_prices

Retrieve GoodRx drug prices by pharmacy for a specific prescription, including coupon, membership, and mail-order costs. Provide drug details and location-based pricing for US pharmacies.

Instructions

Get GoodRx drug prices by pharmacy. Returns GoodRx coupon, membership, and mail-order prices by pharmacy for one drug and prescription (brand/generic label, form, dosage, quantity), plus the drug summary, the priced configuration, the location prices were computed for, and every available label/form/dosage/quantity. Omit label/form/dosage/quantity for GoodRx's default prescription; values must come from /goodrx/drug-options. Pass latitude and longitude (optionally zip_code and state) to price at a US location; otherwise prices reflect a US location chosen by GoodRx. Requests use US egress because GoodRx is US-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formNoForm slug from /goodrx/drug-options
slugYesDrug slug from /goodrx/drugs, /goodrx/class, or /goodrx/condition-drugs
labelNoBrand or generic label slug from /goodrx/drug-options
stateNoTwo-letter state code of that location
dosageNoDosage slug from /goodrx/drug-options
latitudeNoLatitude of a US location to price at (requires longitude)
quantityNoQuantity (1-999999); /goodrx/drug-options lists GoodRx's standard quantities
zip_codeNoFive-digit ZIP code of that location
longitudeNoLongitude of a US location to price at (requires latitude)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does so well: it discloses the location fallback (GoodRx-chosen US location when none supplied), the US-only egress constraint, and the default-prescription behavior. It adds context beyond the schema, though it does not explicitly restate the read-only nature of the call.

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 the core purpose, then returns, then parameter sourcing, then location, then the egress caveat. It is a dense paragraph but each sentence contributes; only mild tightening is possible.

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 nine params, no output schema, and no annotations, the description supplies the return shape, parameter sourcing constraints, and location behavior, which is nearly everything an agent needs. A brief note on read-only semantics or auth would make it fully complete.

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 already 100%, so baseline is 3. The description adds meaning by tying latitude/longitude together (they pair), noting zip_code/state are optional, and explaining that label/form/dosage/quantity must originate from /goodrx/drug-options and can be omitted. This is genuine value beyond the schema descriptions.

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 prices), scoped by pharmacy for a single drug and prescription. It also clarifies the differentiator versus sibling goodrx_drug_options by noting label/form/dosage/quantity values must come from it. An agent can identify the tool 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 Guidelines4/5

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

Gives clear context: omit label/form/dosage/quantity to get the default prescription, and pass lat/long (optionally zip/state) to price at a US location. It routes parameter sourcing to the sibling /goodrx/drug-options. It stops short of an explicit 'use this instead of X when Y', so not quite 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