Skip to main content
Glama

FineRx

by com.finerxfinder
OverviewDiscussionsAdmin

get_prescription_options

Read-onlyIdempotent

Routes to filling a prescription, including having none yet.

Use when the person says they have no prescription, asks how to get one, or
says the brand costs too much. Optional ``drug`` is a slug from
search_drugs (a name works too). Returns three sections — havePrescription
(steps), noPrescription (clinics and telehealth, each with the disclosure
to read out when FineRx earns anything), brandCostly — plus a Medicaid
note, where the drug's card prices start (dated), and the card. For
controlled or age-restricted medicines it returns only ``restricted:
true``: FineRx shows card prices and the card for them, nothing else. Not
medical advice: never say what to take or at what dose.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
drugNo
localeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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_prescription_optionsDictOutput",
-  "type": "object"
-}New value: +null
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the readOnly/idempotent annotations: it details the three returned sections, the restricted-only response for controlled/age-restricted medicines, the disclosure requirement when FineRx earns anything, the Medicaid note, and the non-medical-advice guardrail. This is rich, non-redundant disclosure.

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 front-loaded with purpose and usage, then packs necessary output, exception, and safety behavior into a dense but non-redundant paragraph. Every sentence carries meaningful information; no filler.

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 compensates well by enumerating return sections and the restricted branch. The main gap is the unexplained 'locale' parameter, which prevents full contextual completeness for an agent deciding what to pass.

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

Parameters3/5

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

The description usefully explains the 'drug' parameter as a slug from search_drugs and notes that a name also works, adding meaning beyond the schema. However, the 'locale' parameter is never mentioned, leaving one of the two parameters unexplained despite 0% schema description coverage.

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 clearly states a specific action—routing to filling a prescription—and covers the no-prescription case. It names concrete output sections and implicitly distinguishes itself from price/comparison siblings by focusing on prescription acquisition steps.

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 states when to use the tool: when the person has no prescription, asks how to get one, or says the brand costs too much. It does not explicitly name alternatives or state when not to use it, 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 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