Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goodrx_classes

List GoodRx drug classes with names, URLs, and slugs to look up each class. Returns a cached copy up to a day old if GoodRx is unreachable.

Instructions

List GoodRx drug classes. Lists the drug classes in GoodRx's class directory, such as ACE Inhibitors, with each class name, GoodRx URL and the slug used to look up that class. If GoodRx is unreachable, a retained copy up to about a day old is returned and flagged with an X-Availability-Mode: stale header.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4/5.0
Behavior4/5

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

With no annotations the description carries the burden, and it discloses a non-obvious fallback: an unreachable GoodRx returns a ~1-day-old retained copy flagged with an `X-Availability-Mode: stale` header. That is genuine behavioral context beyond the schema. It does not cover pagination or rate limits, but for a parameterless read listing those are minor.

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?

Two sentences, front-loaded with the core action, then the return fields, then the fallback caveat. No filler; every clause adds information.

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?

For a simple parameterless listing with no output schema, the description covers purpose, the returned fields (name, URL, slug), and the stale-cache behavior. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. The description appropriately spends no effort on parameter semantics and instead documents the return shape.

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 ("List GoodRx drug classes") and clarifies it is the class directory, giving an example (ACE Inhibitors). It does not explicitly distinguish itself from the singular sibling goodrx_class, but the mention of the `slug` used to look up a class implies the relationship.

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?

Usage is implied: this is the directory listing whose `slug` feeds a later lookup (goodrx_class). There is no explicit when-to-use / when-not or named alternative, so an agent must infer its place in the flow.

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