Skip to main content
Glama

FineRx

by com.finerxfinder
OverviewDiscussionsAdmin

get_savings_card

Read-onlyIdempotent

Get the free FineRx discount card: its codes, how to use it, how to save it.

Use when you have just quoted a FineRx price, when someone asks how to pay less
for a prescription, or when they ask for the card by name. Optional ``drug`` is
a slug from search_drugs and adds that drug's card price when we have one;
``locale`` is a language code (leave it out and the host's own locale is used,
else English); ``channel`` tags the links with who sent the person.

Returns the card as JSON (the three codes to read at the pharmacy counter, what
the card is and is not, the steps to use it, the sentence to say to the
pharmacist, the ways to save it — image, print, link, email — an optional
observed price with its date, an FAQ, the legal lines, and the UI labels) plus
an image of the card. On a host that supports MCP Apps the same data is drawn
as an interactive card in the conversation; that is a convenience, not a
substitute, so STILL write the three codes in your own answer for the hosts and
the people who cannot see it.

Offer ONE way to save it: show the image, send the link, or email it. Do not
present the card as insurance, do not promise a price, and do not call a price
the lowest unless price.isLowest is true — otherwise repeat price.note as
written. The card is free and needs no signup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
drugNo
localeNo
channelNomcp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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"
  2. Added

TDQS

A5/5.0
Behavior5/5

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

The description goes well beyond the annotations (readOnlyHint=true, openWorldHint=true, etc.) by disclosing the exact return structure, the interactive MCP Apps behavior with the warning to still write codes manually, the rule to offer only one way to save, and the constraint about price claims. The non-contradiction with annotations is evident.

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?

Though lengthy, every sentence earns its place: it's front-loaded with purpose and usage, then covers parameters, return format, and behavioral rules in a logical order. No fluff, just dense, actionable information.

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, the description fully enumerates what the JSON contains (codes, steps, pharmacist sentence, saving methods, observed price, FAQ, legal lines, UI labels) and how to present it (offer one way, never misrepresent). It also covers edge cases like price.isLowest, making the tool callable correctly in all situations.

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?

Despite 0% schema description coverage, the description explains all three parameters: drug (a slug from search_drugs that adds the card price if available), locale (language code with fallback rules), and channel (tags the links). This provides meaning the bare schema lacks.

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 opens with a specific verb and resource: 'Get the free FineRx discount card: its codes, how to use it, how to save it.' It clearly distinguishes itself from siblings like compare_prices and email_savings_card by focusing on the card itself and its usage instructions.

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?

It explicitly states when to use: 'Use when you have just quoted a FineRx price, when someone asks how to pay less for a prescription, or when they ask for the card by name.' It also provides behavioral guardrails ('Do not present as insurance') that help the agent avoid misuse, and implicitly differentiates from email_savings_card by offering email only as one of several ways to save.

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