Skip to main content
Glama

MenoCost.com: US menopause care prices

Prices of one menopause service

find_menopause_service_prices
Read-onlyIdempotent

Every published menopause treatment price of one US online service (Midi Health, Alloy, Winona, Evernow, Hone Health and others), lowest first, with its fees, insurance and the page each was read on.

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": {
      "service": "<service>"
    },
    "name": "find_menopause_service_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYesThe service's name, e.g. "Alloy".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety needs no restating. The description adds real behavioral context beyond them: results are ordered lowest first, each row carries fees and insurance details, and the source page is included as provenance.

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?

A single sentence that front-loads scope, then sort order, then returned fields. No filler and nothing repeated from the title.

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 must describe returns, and it does: prices, fees, insurance and source page. Missing only edge-case behavior such as an unknown service name or partial coverage per service.

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% and the schema already gives an example value, so baseline is 3. The description goes further by enumerating accepted service names (Midi Health, Alloy, Winona, Evernow, Hone Health and others), which meaningfully helps an agent construct a valid argument.

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 names a specific resource (every published menopause treatment price) and scopes it to exactly one US online service, with the sorted order and returned fields spelled out. It distinguishes itself from the treatment-level and pharmacy-level siblings only by implication ('one US online service'), not by an explicit contrast, so it falls just short of a 5.

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: pass a service name to get that service's prices. There is no explicit statement of when to pick this over find_menopause_treatment_prices or find_menopause_pharmacy_cash_prices, and no guidance on prerequisites or when it is not appropriate.

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