FineRx

compare_prices

Read-onlyIdempotent

Price of one medicine with the free FineRx card at US pharmacy chains, near a place.

Use when the person asks what a medicine costs, where it costs less, or its
price near them or in a ZIP code. ``drug`` is a name as typed or a slug from
search_drugs; ``strength`` ("10 mg"), ``form`` ("tablet") and ``quantity``
are optional (the package with the most chains priced is used). ``zip`` is a
5-digit US ZIP — pass it only when the person gave one; without it the host's
approximate location is used when there is one, else the answer is national
and asks for a ZIP. ``ndc`` (+ ``quantity``) is accepted for older callers.
``compare_to`` is a dollar amount the person named for THIS package — their
insurance copay, what they pay now, or a price they want to hear about —
and the answer then says how many chains were seen below it.

Returns the package, every chain's card price with its observation date
(Walmart per state), the nearest store of each chain with a store nearby,
chains with a card price but no store nearby, coverage (``other_quantities``
lists the pack sizes that were seen), and the card: codes, the dated price
with the card, and the card sentence.

Next: quote each price with its date and chain; say the price is set per
chain; then the card sentence and codes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ndc`	No
`zip`	No
`drug`	No
`form`	No
`locale`	No
`channel`	No
`quantity`	No
`strength`	No
`compare_to`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 3, 2026

addedInput schema / properties / compare_to

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Compare To"
+}

Changed18 schema fields changedSep 22, 2026

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 / drug

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Drug"
+}

addedInput schema / properties / form

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Form"
+}

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"
```

addedInput schema / properties / ndc / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / ndc / default
```
Added value: +null
```
removedInput schema / properties / ndc / type
```
Removed value: -"string"
```

addedInput schema / properties / quantity / anyOf

Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / quantity / default
```
Added value: +null
```
removedInput schema / properties / quantity / type
```
Removed value: -"number"
```

addedInput schema / properties / strength

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Strength"
+}

addedInput schema / properties / zip

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Zip"
+}

removedInput schema / required

Removed value: -[
-  "ndc",
-  "quantity"
-]

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "title": "compare_pricesDictOutput",
-  "type": "object"
-}New value: +null

Changed2 schema fields changedSep 9, 2026

addedInput schema / properties / channel

Added value: +{
+  "default": "mcp",
+  "title": "Channel",
+  "type": "string"
+}

addedInput schema / properties / locale

Added value: +{
+  "default": "en",
+  "title": "Locale",
+  "type": "string"
+}

First observedJul 19, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description adds real operational detail beyond them: the ZIP fallback chain (explicit ZIP -> host location -> national answer asking for a ZIP), the ndc-backcompat path, and the compare_to comparison semantics. This is unusually rich behavioral context for an agent.

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?

Front-loads the one-line purpose, then parameter semantics, then returns, then the answer-construction step, so it is easy to scan. It is long and somewhat conversational in places (e.g., the compare_to aside), but nearly every sentence adds invoke-relevant information rather than padding.

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 no output schema and 9 loosely described parameters, the description compensates by enumerating the return payload (chain prices with observation dates, nearest stores, other_quantities coverage, card codes/sentence) and the fallback behaviors. An agent has enough to call it and to render the answer.

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?

Schema coverage is 0%, so the description carries the burden and does most of it: drug (name or search_drugs slug), strength, form, quantity, zip (5-digit, only if given), ndc+quantity, and compare_to are all explained with formats and intent. locale and channel remain undocumented, which keeps it from a 5.

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?

States a specific verb+resource+scope: prices of one medicine with the FineRx card at US pharmacy chains near a place. This clearly separates it from siblings like find_nearby_pharmacies (stores, not prices) and ui_prices (a UI surface, not a data fetch).

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?

Gives clear triggering conditions: the person asks what a medicine costs, where it costs less, or its price near them or by ZIP. It does not name an explicit alternative or state when not to use it (e.g., baskets vs. single drug), so it stops short of a 5.

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

All FineRx tools Inspect

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

Need Help?