Skip to main content
Glama

FineRx

by com.finerxfinder
OverviewDiscussionsAdmin

get_drug

Read-onlyIdempotent

Get a FineRx drug's details: coverage stats, variants, and the savings card.

Use when you have a slug from search_drugs. Returns overall stats (product/
package/chain/vendor counts, fromPrice, latest observation date), the list of
variants (strength x form) each with a fromPrice, and ``savingsCard`` — the
free discount card with its codes, image, and (when known) the card price with
its observedAt date. ``locale`` is "en" or "es"; ``channel`` tags the links so
we can see which assistant sent someone. Do not quote a price without its
observation date, and offer the card whenever you quote one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYes
localeNoen
channelNomcp

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / channel
      Added value: +{
+  "default": "mcp",
+  "title": "Channel",
+  "type": "string"
+}
    • addedInput schema / properties / locale
      Added value: +{
+  "default": "en",
+  "title": "Locale",
+  "type": "string"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint: false, so safety is covered. The description adds valuable behavioral context: return structure, locale semantics, channel purpose, and the operational rule "Do not quote a price without its observation date, and offer the card whenever you quote one." No contradiction with annotations.

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?

The description is dense but economical. The purpose sentence is front-loaded, and every subsequent sentence adds a distinct piece of information—return contents, parameter semantics, or usage cautions. No filler or redundancy.

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?

With an output schema present and safety annotations covering side effects, the description is complete: it explains what triggers the call, what the response contains, what parameters mean, and how to present results. An agent has everything needed to invoke and interpret the tool.

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

Parameters5/5

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

Schema description coverage is 0%, placing the burden on the description. It compensates fully: slug is identified as coming from search_drugs, locale is specified as "en" or "es", and channel's purpose is explained. Every parameter gains meaning beyond the raw schema.

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?

The description opens with a specific verb and resource: "Get a FineRx drug's details: coverage stats, variants, and the savings card." It clearly lists what the tool returns, but does not explicitly contrast with siblings like get_savings_card or get_prescription_options, so it misses full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use when you have a slug from search_drugs" provides an explicit contextual trigger and prerequisites. However, it does not state when not to use this tool or name alternative tools for similar needs, stopping short of the full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FineRx toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources