List all GoodRx drug classes and retrieve their slugs for /goodrx/class pages. Use it to discover the full class directory before building links or searches.
List GoodRx drug classes. Returns every drug class in GoodRx's class directory with slugs for /goodrx/class.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does disclose that the entire class directory is returned (no filtering) and that each entry carries a slug usable against /goodrx/class, which is useful. It says nothing about result size, ordering, or completeness guarantees, but the tool is a trivial read.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, zero waste, with the resource and the return payload front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a no-parameter, no-annotation, no-output-schema list tool, the description covers what is returned and the slug format. The only real gap is the lack of differentiation from the singular goodrx_class sibling.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies for a no-arg tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) and resource (GoodRx drug classes), and specifies the returned payload (every class with slugs for /goodrx/class). It does not distinguish itself from the singular sibling goodrx_class, so an agent must infer which one to use.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance, prerequisites, or alternative routing. The existence of goodrx_class (single class) makes an explicit boundary important, yet the description never mentions it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.