FineRx

find_nearby_pharmacies

Read-onlyIdempotent

Pharmacy stores within 30 miles, per chain — with the card price when a drug is given.

Use when the person asks where the pharmacies are near a ZIP or near them.
``zip`` is a 5-digit US ZIP (leave it out to use the host's approximate
location when there is one). ``family`` is a comma-separated list of chain
codes: walmart, cvs, walgreens, kroger, albertsons, costco, publix, heb,
hyvee, meijer, wegmans, shoprite, bigy, gianteagle, kinney (``chains`` is the
older name of the same filter). With ``drug`` (+ optional strength, form,
quantity) each store carries its chain's card price and observation date.

Returns stores (chain, address, city, distance, whether it is a pharmacy or a
store with a pharmacy inside — not verified) and the card. Stock is not
visible: suggest calling ahead. Coordinates © OpenStreetMap contributors.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`zip`	No
`drug`	No
`form`	No
`limit`	No
`chains`	No
`family`	No
`locale`	No
`quantity`	No
`strength`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedSep 22, 2026

addedInput schema / properties / drug

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

addedInput schema / properties / family

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

addedInput schema / properties / form

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

addedInput schema / properties / locale

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

addedInput schema / properties / quantity

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Quantity"
+}

addedInput schema / properties / strength

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

addedInput schema / properties / zip / anyOf

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

addedInput schema / properties / zip / default
```
Added value: +null
```
removedInput schema / properties / zip / type
```
Removed value: -"string"
```
removedInput schema / required
```
Removed value: -[
-  "zip"
-]
```

changedOutput schema / (root)

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

First observedJul 19, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description correctly adds non-contradictory behavioral details: returns store fields and card info, explicitly states 'Stock is not visible: suggest calling ahead,' and flags that pharmacy-vs-store-with-pharmacy is 'not verified.' It also attributes map data, which is helpful context beyond the annotations.

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 front-loaded with a one-sentence summary, then flows into usage, parameter details, and return behavior. Each sentence adds unique value (chain codes, caveats, attribution) with no filler. It is longer than the bare minimum but appropriate for the 9-parameter surface.

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?

For a 9-parameter tool with no output schema, the description explains return contents (stores fields, card price, observation date) and the stock visibility limitation. It leaves minor gaps (limit behavior, locale meaning) but overall provides enough for an agent to call correctly and set user expectations about stock and verification.

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?

With 0% schema description coverage, the description carries the burden and compensates well: it explains zip (5-digit, optional with host location), family (with chain codes and the chains alias), and drug plus optional strength/form/quantity. However, limit and locale are not explained, leaving two parameters underdocumented. The coverage is substantial but not complete.

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 opening sentence precisely states the action and scope: 'Pharmacy stores within 30 miles, per chain — with the card price when a drug is given.' This distinguishes it from siblings like search_drugs or get_savings_card by specifying the geographic and chain-filtering behavior. The 'Use when' clause reinforces the exact user intent (near a ZIP or near them), making the tool's role unambiguous.

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?

The description explicitly says 'Use when the person asks where the pharmacies are near a ZIP or near them,' giving a clear trigger condition. It does not, however, name alternative tools or state when not to use this tool, leaving some routing judgment to the agent. This is clear context without exclusions, matching the score 4 criterion.

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?