Skip to main content
Glama

MenoCost.com: US menopause care prices

Cash prices at a pharmacy

find_menopause_pharmacy_cash_prices
Read-onlyIdempotent

What a menopause medicine costs at a cash pharmacy without insurance, with a prescription: Mark Cuban Cost Plus Drugs' own published prices for the brand and its generic (estradiol tablets, patches, gel, vaginal cream, inserts and ring, progesterone, Prempro, Activella, Premarin, paroxetine 7.5 mg), a pharmacy membership's flat monthly price where its own page names the medicine (Amazon Pharmacy RxPass for estradiol tablets), and for brands Cost Plus does not sell, what US pharmacies pay (CMS NADAC) and the maker's savings program. Accepts a treatment or a brand: "estradiol patch", "progesterone", "Premarin", "Estring", "Imvexxy". Returns each product, strength, pack, price before shipping, shipping, the day read, the source, and the page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "find_menopause_pharmacy_cash_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA treatment or a brand, e.g. "estradiol pill" or "Premarin".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the description's job is added context — and it delivers: it names every upstream source, states that prices are 'before shipping' with shipping reported separately, and flags 'the day read' and 'the page' as returned provenance fields. That freshness-and-provenance caveat is behavior an agent would otherwise not know. It stops short of saying how prices are ordered or what happens when a query matches nothing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the opening clause, which is good, but the whole definition is a single sprawling sentence with two long parenthetical enumerations of formulations and brands. The enumerated product list earns some of its space by communicating data coverage, yet the density makes it harder to scan than a short split structure would.

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?

There is no output schema, and the description compensates by enumerating exactly what is returned: product, strength, pack, price before shipping, shipping, day read, source, and page. Combined with annotations covering the safety profile and a fully documented input, an agent has what it needs to call and interpret this tool. The one real gap is the unexplained boundary with the NADAC-focused sibling.

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 coverage is 100% and the single query parameter already carries its own description with examples, so the schema does the heavy lifting. The description adds some accepted vocabulary beyond the schema — brand names like Estring and Imvexxy, and the treatment-or-brand duality — but supplies no normalization or matching rules for unmatched terms, so it is only a modest increment over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: cash prices for menopause medicines without insurance, sourced from Cost Plus Drugs, RxPass, CMS NADAC, and maker savings programs, with an explicit list of covered products. The agent can tell this is a retail cash-price lookup, not a service or treatment-cost lookup. It does not, however, distinguish itself from the sibling menopause_pharmacy_cost_nadac despite openly including NADAC figures for brands Cost Plus doesn't sell.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The self-pay, prescription-in-hand, uninsured framing implicitly signals when this tool applies, and 'cash pharmacy without insurance' is a usable contextual cue. But there is no explicit when-not guidance and no routing to alternatives, which matters because the description's own mention of CMS NADAC overlaps with the dedicated menopause_pharmacy_cost_nadac sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources