Skip to main content
Glama

FineRx

by com.finerxfinder
OverviewDiscussionsAdmin

email_savings_card

Destructive

Email the free FineRx discount card to an address the person gave you.

Use ONLY after the person has given an email address AND confirmed they want
the card sent there — ask for both first, then set ``consent`` to true. The
message contains the card and nothing else; FineRx does not store the address.

Returns ``sent`` true with the masked address, or ``sent`` false with the
reason. On an error, say what happened and offer the printable card or the
link instead. Do not retry a refusal or read the full address back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYes
localeNo
consentNo

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": "email_savings_cardDictOutput",
-  "type": "object"
-}New value: +null
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description states that FineRx does not store the address, that the message contains only the card, that the response includes a masked address, and that the full address should not be read back. This is useful behavioral and privacy context that annotations do not provide.

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 the action, then preconditions, then return behavior and error handling. Every sentence adds operational value and none are redundant or overly verbose.

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?

Since there is no output schema, the description fully explains the return contract: sent true with a masked address or sent false with a reason. It also covers consent, privacy, error handling, and fallback options, making it complete for an agent to invoke correctly.

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 compensates well for email and consent: it explains email as the person-provided address and consent as a required flag set to true only after confirmation. However, the locale parameter is not mentioned at all, leaving a small semantic gap.

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: 'Email the free FineRx discount card to an address the person gave you.' This clearly identifies the action and distinguishes it from siblings like get_savings_card, which would retrieve or generate a card rather than send it.

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 gives explicit preconditions: use ONLY after the person has provided an email and confirmed they want it sent, and it instructs setting consent to true. It also defines fallback behavior on error by offering the printable card or link and says not to retry a refusal.

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