Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goodrx_health_article

Fetch a GoodRx Health article by path or URL to get its headline, authors, key takeaways, sections, FAQs, and references in clean JSON.

Instructions

Get a GoodRx Health article. Returns one GoodRx Health article: headline, description, authors, medical reviewers, published and modified dates, category tag, key takeaways, the body as headed sections of paragraphs and lists, FAQs, references, and related medications. Requests use US egress because GoodRx is US-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesArticle path from /goodrx/health-articles (or a www.goodrx.com article URL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the load and does disclose real behavioral context: the full return shape (headline, authors, reviewers, bodied sections, FAQs, references) and the geographic constraint "Requests use US egress because GoodRx is US-only." It does not cover error/failure behavior, but for a read fetch this is solid.

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 one clause, then the return contents, then the US-egress constraint — a sensible order. Enumerating every returned field is somewhat list-heavy, but each item is informative rather than filler.

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, so the description compensating by enumerating the returned fields is valuable and makes the tool's payload predictable. Combined with the US-only egress note, an agent has enough to call and interpret the tool correctly.

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% and the single required `path` parameter is already documented in the schema as coming from /goodrx/health-articles, so the description adds nothing beyond it. Baseline 3 applies.

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 and resource ("Get a GoodRx Health article") and immediately clarifies it returns ONE article, which distinguishes it from the plural listing sibling goodrx_health_articles without needing to open either 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?

The singular/plural contrast against goodrx_health_articles implies this is the detail fetch after listing, but the description never names that alternative or states the condition for choosing it. Usage is inferable from the name and return shape rather than explicitly guided.

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