Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goodrx_answer

Retrieve a GoodRx health question and answer using a slug from /goodrx/answers, including the short answer, source article, drug, related questions, articles, and medications.

Instructions

Get a GoodRx health question and answer. Returns one GoodRx health question with its short answer, supporting paragraphs, the source article, the drug it is about, more questions about that drug, related articles, and related medications. Use a slug from /goodrx/answers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesQuestion slug from /goodrx/answers

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does so well by detailing the entire return payload (answer, paragraphs, source article, drug, related questions/articles/medications). It doesn't mention error behavior for an invalid slug or any auth/rate limits, but for a read-only fetch the disclosed return shape is substantial.

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-loaded with the core action in sentence one and the input requirement last. The middle sentence is a long enumeration of return fields, which is informative but slightly bulky for the size of the tool.

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

Completeness5/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 must explain the return value — and it does so comprehensively. The single required parameter is documented in both schema and description, leaving nothing an agent needs to call it 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 schema already says "Question slug from /goodrx/answers". The description's "Use a slug from /goodrx/answers" simply restates that, adding no format or syntax detail beyond the structured field, so the baseline of 3 applies.

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 question and answer") and enumerates what comes back. The phrase "Returns one" implicitly distinguishes it from the sibling list tool goodrx_answers, though that sibling is never named outright.

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/answers" gives the prerequisite/source for the input value, which is genuinely useful. However, there is no explicit when-to-use versus alternatives guidance (e.g. when to use this vs. goodrx_answers or goodrx_drug_guide), so usage is only implied.

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