Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goodrx_condition_drugs

List medications for a health condition by slug, returning each drug's lowest displayed price and summary. Use a condition slug with available medications.

Instructions

List GoodRx medications for a condition. Returns the medications GoodRx lists for one health condition, with each drug's lowest displayed price and summary. Use a slug from /goodrx/conditions whose has_medications is true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesCondition slug from /goodrx/conditions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.7/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It discloses the return payload shape (lowest displayed price and summary), which is useful, but says nothing about being a read-only listing, pagination, rate limits, or error behavior for a bogus slug. Adequate but thin for a no-annotation tool.

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?

Two tight sentences, front-loaded with the action, no filler. The precondition is placed at the end where it's easy to act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-param read tool with 100% schema coverage and no output schema, the description covers the essentials (what it returns, which slugs are valid). It's still missing what happens on a non-has_medications slug and whether the price is comprehensive vs. just lowest displayed, but those are secondary.

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 coverage is 100% and the single param already documents itself as 'Condition slug from /goodrx/conditions'. The description adds the important constraint that the slug must have has_medications=true, which is genuinely beyond the schema, but otherwise restates the source endpoint. Baseline 3 given full schema coverage.

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?

States a clear verb and resource ('List GoodRx medications for a condition') and adds scope about return payload (lowest price + summary). It distinguishes itself from the large sibling set generically, but doesn't name a specific sibling such as goodrx_drug_prices or goodrx_condition.

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 a concrete precondition: 'Use a slug from /goodrx/conditions whose has_medications is true.' This is real routing guidance, but it never states alternatives (e.g., goodrx_drug_prices for a known drug) so an agent can't tell when NOT to use it.

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