Skip to main content
Glama

MenoCost.com: US menopause care prices

Prices of a menopause treatment

find_menopause_treatment_prices
Read-onlyIdempotent

US online services' prices for one menopause treatment, lowest 30-day cost first (a membership charged on top included). Accepts a treatment or a product name: "estradiol patch", "progesterone", "vaginal estrogen", "Veozah", "compounded hormones", "Bi-Est", "testosterone for women". Returns each service, product, 30-day cost, the service's own price wording, what starting costs, whether it takes insurance, the day read, the source page, whether this site may earn a referral fee, and the page with every price.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many prices to return. Defaults to 10.
treatmentYesA treatment or product, e.g. "estradiol patch" or "Veozah".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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), so the description earns credit for disclosing behavior the annotations do not: results are sorted by lowest 30-day cost with membership fees folded in, and it enumerates the returned fields including referral-fee disclosure and a source link. There is mild tension between openWorldHint=false and the description's web-derived fields ('the source page', 'the day read'), but this is consistent with serving a cached snapshot rather than live web calls.

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?

Two sentences, with the scope and sort order front-loaded before the input examples. The return-field enumeration is dense and includes awkward fragments ('what starting costs', 'the day read') that cost some clarity, but nearly 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 carries the burden of describing return shape and does so field by field, including the cost semantics of the sort order. Gaps remain around currency, freshness of the price data beyond 'the day read', and behavior when a treatment yields no matching services.

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 100%, so the baseline is 3, but the description goes further by explaining that the input accepts either a treatment or a product name and then supplies seven concrete accepted strings, which materially widens what the agent will try beyond the schema's two examples. The `limit` parameter is left entirely to the schema, which is acceptable given full coverage.

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?

The description states a specific verb and resource (US online services' prices for one menopause treatment) plus the sort order, so the agent knows exactly what this returns. It does not name or route away from the near-identical siblings find_menopause_pharmacy_cash_prices and find_menopause_service_prices, leaving the differentiation to be inferred from the 'US online services' scope.

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 through the accepted-input examples ('estradiol patch', 'Veozah', 'compounded hormones'), which tells the agent what queries are valid. There is no explicit when-to-use or when-not-to-use guidance relative to the pharmacy-cash-price or service-price siblings, so the agent must guess which of the three price tools applies.

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