Skip to main content
Glama

FineRx

by com.finerxfinder
OverviewDiscussionsAdmin

get_drug

Read-onlyIdempotent

Strengths, forms and pack sizes of one medicine that have a card price, and its default package.

Use when you have a slug and need to know which strengths and quantities
exist before quoting a price. Returns ``configs`` (strength × form, each
with quantities, where the card prices for that pack start, with the date,
and how many chains priced it), ``defaultConfig`` (the package the most chains
price), ``fromCardPrice``, the card prices of the default package per chain,
and the card. Next: compare_prices for the package the person takes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYes
localeNo
channelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / channel / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / channel / default
      Previous value: -"mcp"New value: +null
    • removedInput schema / properties / channel / type
      Removed value: -"string"
    • addedInput schema / properties / locale / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / locale / default
      Previous value: -"en"New value: +null
    • removedInput schema / properties / locale / type
      Removed value: -"string"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "get_drugDictOutput",
-  "type": "object"
-}New value: +null
  2. 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"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds value by detailing the return fields (configs, defaultConfig, fromCardPrice, card) and their semantics. It does not contradict annotations and provides additional behavioral context beyond safety.

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?

The description is two paragraphs, front-loads the purpose, and is reasonably structured. It is not overly verbose, though the return-field explanation is a bit dense. It earns its place without redundancy.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must explain return values, which it does by enumerating the fields. It also provides usage context and a clear next step. It lacks explicit handling of optional parameters or error scenarios, but overall it is complete for a read-only lookup.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It only hints at the slug parameter ('Use when you have a slug') but does not explain the locale and channel parameters. This is a significant gap for a tool with 3 parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it retrieves strengths, forms, and pack sizes for one medicine that has a card price, plus its default package. It clearly distinguishes itself from siblings like compare_prices by noting it is the preliminary step before quoting a price.

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

Usage Guidelines5/5

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

Explicitly states when to use it: 'Use when you have a slug and need to know which strengths and quantities exist before quoting a price.' It also names the next step ('Next: compare_prices') which provides an alternative and context for when this tool is appropriate.

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