Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goodrx_condition

Fetch a GoodRx health condition overview by slug, returning titled sections for definition, types, causes, symptoms, diagnosis, medications, treatments, and prevention plus author and date details.

Instructions

Get a GoodRx health condition overview. Returns a health condition's GoodRx overview article as titled sections (definition, types, causes, symptoms, diagnosis, medications, treatments, prevention, references), with the condition's alternate name, authors, publish and modified dates, the medications-list URL, and related articles. Use a slug from /goodrx/conditions.

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
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 it delivers substantial detail: the exact set of titled sections returned, plus alternate name, authors, dates, medications-list URL, and related articles. It stops short of explicitly confirming the operation is read-only or stating any auth/rate-limit behavior, but the disclosed return shape is well beyond what the schema provides.

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-loads the purpose in the first sentence, then packs the return details into the second with no filler. The section enumeration is a long parenthetical but it is information-dense rather than redundant.

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?

There is no output schema and no annotations, so the description must cover the return value on its own, which it does comprehensively. For a single-parameter read lookup it is essentially complete, with only explicit read-only/auth confirmation missing as a minor gap.

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 parameter's description ('Condition slug from /goodrx/conditions') is essentially duplicated verbatim in the tool description. Baseline 3 is appropriate since the schema already does the heavy lifting and the description adds no new parameter meaning.

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 specific verb and resource ('Get a GoodRx health condition overview') and even details the returned article structure, so an agent knows exactly what it fetches. It does not, however, name or differentiate itself from siblings such as goodrx_conditions (list) or goodrx_condition_drugs, leaving that inference to the reader.

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?

'Use a slug from /goodrx/conditions' implies the workflow (fetch the list first, then request a condition) but does not frame it as an alternative to siblings or state any when-not condition. Usage is implied rather than explicit.

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