Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goodrx_comparison

Compare two drugs on GoodRx by slug to retrieve head-to-head key takeaways, both drug names, and their price-page and information slugs. Use a comparison or drug-info slug.

Instructions

Get a GoodRx drug comparison. Returns a GoodRx head-to-head drug comparison's key takeaways and the two drugs compared, with their price-page and information slugs. Use a slug from /goodrx/comparisons or /goodrx/drug-info alternatives.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesComparison slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the return contents (takeaways, the two compared drugs, price-page and info slugs), but says nothing about permissions, rate limits, or error behavior when a slug is invalid. A read getter is inherently low-risk, so a 3 is defensible, but richer context is absent.

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?

Two sentences, front-loaded with the action and followed by the payload description. Nothing is wasted, though the trailing 'or /goodrx/drug-info alternatives' phrasing is slightly confusing.

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, the description does the right thing by enumerating the return contents. For a single-parameter, single-resource getter the coverage is nearly sufficient; only invalid-slug/error behavior is missing.

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 schema already labels the field as 'Comparison slug'. The description adds the provenance of the slug ('from /goodrx/comparisons or /goodrx/drug-info alternatives'), which is marginally useful but somewhat ambiguous about which tool returns which slug.

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+resource ('Get a GoodRx drug comparison') and describes what is returned: key takeaways plus the two drugs and their slugs. It clearly reads as a head-to-head comparison retrieval, distinguishable from the plural goodrx_comparisons list tool, though it never names that sibling explicitly.

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 description tells the agent where to source the input ('Use a slug from /goodrx/comparisons or /goodrx/drug-info alternatives'), which is implied usage guidance. However, it never states when this tool should be chosen over the goodrx_comparisons list or goodrx_drug_info siblings, leaving the routing decision to inference.

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