Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goodrx_drug_guides

List GoodRx drug guides with side effects, dosage, and interactions as drug slug and topic pairs. Filter by topic or first letter to retrieve structured pages for each medication.

Instructions

List GoodRx drug guides. Returns GoodRx's dedicated drug guide pages (side effects, dosage, and interactions) as drug slug and topic pairs with last-modified dates, optionally filtered by topic and by the first character of the drug slug. Use the pairs with /goodrx/drug-guide.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoGuide topic
letterNoFirst character of the drug slug: a-z or 0-9

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?

No annotations are provided, so the description carries the full disclosure burden. It describes the return shape (drug slug + topic pairs with last-modified dates), which is valuable behavioral context. It does not mention pagination, rate limits, or auth, which is a minor gap for a read-only listing 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?

Three tight sentences: purpose first, return format second, routing instruction last. No redundancy, and the most decision-relevant content is front-loaded.

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 no output schema and no annotations, the description does well to describe the returned pairs and their fields, plus the intended downstream use. It is close to complete; only operational details like pagination or result limits are absent.

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%, with the topic enum and letter format (a-z, 0-9) already documented in the schema. The description restates both filters ('by topic and by the first character of the drug slug') without adding syntax or semantics beyond the schema. Baseline 3 is appropriate.

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 (List) and resource (GoodRx drug guides), and pinpoints scope: returns drug guide pages as slug/topic pairs. This clearly distinguishes it from the sibling goodrx_drug_guide (singular), which the description explicitly routes results to.

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?

Explains the filters available (topic, first slug character) and gives a concrete chaining directive: 'Use the pairs with /goodrx/drug-guide.' It lacks an explicit when-to-use-this-vs-goodrx_drugs statement, but the chaining context is clear and actionable.

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