Skip to main content
Glama

FineRx

by com.finerxfinder
OverviewDiscussionsAdmin

get_savings_card

Read-onlyIdempotent

The free FineRx discount card: its codes, how to use it, how to keep it.

Use when the person asks for the card, how to pay less at the pharmacy, or
right after you quoted a card price. Optional ``drug`` (a slug from
search_drugs) adds that drug's card price for its most-priced package, with
the date it was observed. ``locale`` is a language code (the host's own is
used when left out).

Returns the three codes to read at the counter, the steps, the sentence to
say to the pharmacist, the links to the card page and the printable sheet,
and the card sentence with the small print. Hosts with MCP Apps show it as an
interactive card; write the three codes in your answer anyway. The card is
free, needs no signup and is not insurance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
drugNo
localeNo
channelNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds valuable behavioral context: it returns three codes, steps, a sentence to say, links, and the card sentence with small print. It also warns that 'Hosts with MCP Apps show it as an interactive card; write the three codes in your answer anyway' and clarifies the card is free, requires no signup, and is not insurance. No contradiction with 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 a single paragraph that front-loads the purpose, then gives usage triggers, explains parameters, lists return contents, and adds extra notes. Every sentence carries information; there is no fluff. It is compact yet sufficiently detailed for the tool's complexity.

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?

The tool is relatively simple, with no output schema and three optional parameters. The description covers the main return values, usage conditions, and parameter semantics for two of three parameters. It also notes the interactive card behavior. The only missing piece is the 'channel' parameter and any error or edge-case handling, but overall the description is sufficient for an agent to call the tool correctly.

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?

Schema description coverage is 0%, so the description must explain all parameters. It explains 'drug' (a slug from search_drugs, adds the card price for the most-priced package with the observation date) and 'locale' (a language code, defaults to host's own). However, the 'channel' parameter is not mentioned at all, leaving a gap for an agent deciding whether to set it. Since two of three parameters are well described but one is omitted, a score of 3 is appropriate.

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 'The free FineRx discount card: its codes, how to use it, how to keep it,' which clearly states the tool's purpose as providing card details. It also specifies trigger conditions ('Use when the person asks for the card, how to pay less at the pharmacy, or right after you quoted a card price') that differentiate it from sibling tools like email_savings_card or compare_prices, making its scope 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?

Explicit usage triggers are given ('Use when...') that tell an agent exactly when to invoke the tool. It also explains the optional parameters' effect (drug adds price, locale defaults to host's own). However, it does not explicitly mention when NOT to use it or compare to alternatives, though the triggers are clear enough to avoid misuse.

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