Skip to main content
Glama

MenoCost.com: US menopause care prices

Boxed warning on menopause hormone labels, today

menopause_boxed_warning_status
Read-onlyIdempotent

Where the current FDA labels of menopause hormone therapy stand on the boxed warning FDA asked makers to change on 10 Nov 2025, as FDA's label database (openFDA) reads today: per treatment, how many makers' labels carry the updated (endometrial-only) warning, none, or the full warning with cardiovascular and dementia language, and each label's brand, maker, route and date. Optional treatment, e.g. "estradiol patch".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "menopause_boxed_warning_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
treatmentNoOptional: a treatment, e.g. "estradiol patch" or "progesterone".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish a safe, read-only, deterministic lookup, so the bar is lower. The description still adds real context beyond them: the upstream source (openFDA label database), the snapshot nature ("as FDA's label database reads today"), and the three warning-state buckets it reports, which tells the agent how to interpret results rather than just that a read occurred.

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 purpose and the source are front-loaded in the first clause, and the return shape is enumerated compactly in a single dense sentence. It is longer than strictly necessary and repeats the parameter example already present in the schema, but no sentence is wasted.

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?

There is no output schema, and the description compensates by spelling out the per-treatment counts, the three warning categories, and the per-label fields (brand, maker, route, date). Combined with the source and time qualifier, an agent has everything needed to call it and interpret the response.

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 optional parameter is already documented with an example. The description restates optionality and repeats an example treatment, adding no new syntax or matching behavior (e.g., whether partial names match), so this sits at the baseline.

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 names a specific resource (FDA boxed-warning status on menopause hormone therapy labels) and a specific operation (report where each treatment and maker stands as of a stated date). It is immediately distinguishable from siblings like menopause_fda_actions or list_menopause_treatments, which do not report per-maker label warning states.

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?

Usage is implied by the framing: query it when you need current label warning status, optionally narrowed to one treatment such as "estradiol patch". There is no explicit statement of when not to use it or which sibling to pick for adjacent questions (e.g., regulatory actions vs label text), so the agent must infer routing.

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