Skip to main content
Glama

MenoCost.com: US menopause care prices

What pharmacies pay (CMS NADAC)

menopause_pharmacy_cost_nadac
Read-onlyIdempotent

What US retail pharmacies pay per unit for a menopause medicine and each of its strengths and brands, from CMS's weekly NADAC survey (newest week, and the week before when it moved). A pharmacy's cost, not a price a person pays. Accepts a treatment or a product word, e.g. "estradiol patch", "Prometrium", "Veozah".

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": "menopause_pharmacy_cost_nadac"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description rightly spends its words elsewhere: it discloses the upstream source (CMS weekly NADAC survey) and the recency policy (newest week, plus the prior week when the figure moved). It does not discuss lookup failures or what an unknown drug name returns.

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?

Three sentences, front-loaded with the core claim, then the disambiguation, then the input contract. No filler and nothing is deferred to later in the text.

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 available, the description still tells the agent what comes back: per-unit costs across each strength and brand, at current-week granularity with a prior-week comparison. That, plus source and input shape, is everything needed to call a single-parameter lookup 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?

Schema coverage is 0% for the single `query` parameter, so the description has to carry the load and does: it specifies that either a treatment phrase or a product/brand word is valid and gives three concrete examples spanning a generic form, a brand, and a newer drug. It does not state matching rules (partial vs exact, case handling).

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?

Names a specific resource and metric: per-unit cost US retail pharmacies pay for a menopause medicine, broken out by strength and brand, sourced from CMS NADAC. The line "A pharmacy's cost, not a price a person pays" explicitly separates it from the cash-price sibling, so an agent can route without opening a schema.

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 "pharmacy cost, not a price a person pays" framing effectively says when to pick this over find_menopause_pharmacy_cash_prices, and "Accepts a treatment or a product word" tells the agent what input shape is in scope. It stops short of naming the alternative tool outright or stating exclusions such as non-menopause drugs.

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