Skip to main content
Glama

MenoCost.com: US menopause care prices

What Medicaid and Medicare paid

menopause_public_payers
Read-onlyIdempotent

What Medicaid paid per prescription (CMS State Drug Utilization Data, newest four quarters) and what Medicare drug plans paid per claim (CMS Part D Prescribers by Geography and Drug, newest year) for a menopause treatment, nationally or in one US state, with each drug's Medicare spending per unit over five years. What a payer paid, not a price a person pays. Accepts a treatment, e.g. "estradiol patch", and an optional two-letter state code, e.g. "TX".

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": {
      "treatment": "<treatment>"
    },
    "name": "menopause_public_payers"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoTwo-letter US state code; national when left out
treatmentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add data-shape context. It does add valuable specifics — aggregations per prescription, per claim, per unit, plus the time windows (newest four quarters, newest year, five years) — but says nothing about freshness caveats, missing-state behavior, or how unmatched treatment names are handled.

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?

Dense but front-loaded: the primary metric and source appear in the first clause, and the 'payer paid, not a price a person pays' caveat earns its place as a disambiguator. The final sentence on accepted inputs is slightly redundant with the opening but still useful.

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?

With no output schema and annotations carrying the safety profile, the description adequately specifies what comes back: per-prescription Medicaid figures, per-claim Medicare figures, and five-year per-unit spending. The main remaining gap is error/empty-result behavior for unrecognized treatments or states.

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 only 50% (treatment is undocumented in the schema), and the description compensates well by giving a concrete example input ('estradiol patch') and clarifying that state is an optional two-letter code with national default. It stops short of describing matching behavior or format tolerances for treatment strings.

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 the specific verb and resources ('What Medicaid paid per prescription', 'what Medicare drug plans paid per claim'), attributes the data sources (CMS State Drug Utilization Data, CMS Part D Prescribers by Geography and Drug), and scopes it to a menopause treatment, nationally or per state. This clearly separates it from siblings like find_menopause_pharmacy_cash_prices and menopause_pharmacy_cost_nadac.

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 line 'What a payer paid, not a price a person pays' explicitly signals when this tool is the right one versus consumer-facing price tools, and it states the accepted inputs. It does not name a sibling alternative or state exclusions, so it falls short of a 5.

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