Search FineRx for drugs by name or localized alias.
Returns candidate drugs with their slug (use it with get_drug), kind
(generic/brand), and lowest observed public price (fromPrice). Use this
first to resolve a drug name to a slug.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds value by specifying the return fields (slug, kind, fromPrice) and search scope, which are not in annotations. No contradictions.
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?
Three concise sentences: first states purpose, second lists outputs, third gives usage guidance. No unnecessary words, and the structure is front-loaded with the most important information.
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?
Given the tool's simplicity, good annotations, and presence of an output schema, the description is complete. It covers what, how, and when, and the return fields are described even though the output schema exists, adding practical context.
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?
Schema description coverage is 0%, so description must compensate. It explains that 'query' is the drug name or alias, but does not mention the 'limit' parameter or its default. Partial compensation; could be improved by noting limit restricts results.
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?
The description clearly states the tool searches FineRx for drugs by name or localized alias, specifying the resource (drugs) and scope (FineRx). It distinguishes from siblings like get_drug (for retrieving a specific drug by slug) and compare_prices (pricing comparison).
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?
The description explicitly instructs 'Use this first to resolve a drug name to a slug', providing clear when-to-use guidance and implying the alternative (get_drug) for subsequent steps. This leads the agent to the correct workflow.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a distinct function: searching drugs, getting drug details, comparing prices, finding pharmacies, and retrieving dataset metadata. There is no overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., search_drugs, compare_prices, get_drug), making the set predictable and easy to navigate.
With 5 tools, the server is well-scoped for a drug pricing API. Each tool addresses a specific step in the typical workflow (search, details, price comparison, location, metadata), and the count is neither too small nor excessive.
The toolset covers the core workflow: search drugs, retrieve drug details, compare prices, find pharmacies, and obtain dataset info. A minor gap is that the mechanism to obtain an NDC from a drug is implied but not explicitly detailed, though the flow likely works.