Skip to main content
Glama

MenoCost.com: US menopause care prices

FDA actions on menopause treatments

menopause_fda_actions
Read-onlyIdempotent

FDA's approvals, generic approvals, label changes and safety notices for menopause treatments (estradiol, conjugated estrogens, progesterone, Veozah, Lynkuet, paroxetine 7.5 mg), newest first, each dated with its source, read from FDA's records each day. Optional treatment filter.

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_fda_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
treatmentNoOptional: a treatment, e.g. "Veozah".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description still adds real behavior: the data is refreshed daily from FDA records and results carry a per-item date and source, which is useful context not in the annotations. It omits pagination/truncation behavior.

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?

A single front-loaded sentence that packs scope, ordering, provenance and freshness without filler, followed by a short note on the optional filter. Slightly dense but every clause carries information.

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, the description does the needed work by saying each result is dated and sourced and comes newest-first. Enough for correct invocation, though the absence of any limit/pagination guidance and default page size leaves a small gap.

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?

At 50% schema coverage, the treatment parameter is documented in both schema and description (with brand examples like Veozah), but the limit parameter is never mentioned in the description and the schema gives it only a 1-25 bound with no explanation of default or ordering interplay. The description therefore adds little beyond 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 plus the exact record types covered (approvals, generic approvals, label changes, safety notices) and names the drug classes and brands in scope, e.g. estradiol and Veozah. The regulatory-action focus is inherently distinguishable from the price/payer siblings, though it never explicitly contrasts with them.

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?

Implies a browse-newest-first workflow via 'newest first' and offers an 'Optional treatment filter' for narrowing, which hints at when to supply the parameter. It gives no explicit when-to-use vs when-not guidance and names no alternative tool for price or warning-status questions.

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