Skip to main content
Glama

Find HRT Prices

find_hrt_prices
Read-only

Current US self-pay prices of menopause hormone therapy (HRT) programs from HRT Buyer Guide's dated records, returned in the guide's ranked order (score-based). An optional form filter (topical, patch or oral) limits results to programs whose recorded price covers that form. Each result names its source page and check date.

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

Input Schema

NameRequiredDescriptionDefault
formNo

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 establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: results come back in the guide's score-based ranked order, records are dated, and each result carries its source page and check date, which signals the data may be stale. It does not discuss result counts or how often records refresh.

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?

Three tight sentences, each doing distinct work: what the data is, how the filter behaves, and what each result contains. The ranked-order detail is front-loaded with the core purpose rather than buried, and there is no redundant restatement of 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?

For a one-optional-parameter, read-only lookup with no output schema, the description covers source, ordering, filter semantics, and per-result attribution well. The notable gap is price units — it says 'self-pay prices' but never specifies currency or billing period (monthly vs. annual), which an agent would need to interpret the numbers.

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 description coverage is 0%, so the description carries the burden for the single 'form' parameter. It does add real meaning by explaining that the filter limits results to programs whose recorded price covers that form — a matching rule the bare enum cannot convey. However, it doesn't clarify behavior for programs with no recorded form, which leaves a meaningful edge case undefined.

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 gives a specific verb-and-resource: current US self-pay prices of menopause HRT programs, sourced from HRT Buyer Guide's dated records and returned in ranked order. Scope, geography, and data source are all stated, so an agent knows exactly what dataset this covers. It does not name or distinguish itself from the sibling find_provider_hrt_prices, so it stops 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 rather than stated: it's clearly the tool for browsing program-level HRT pricing, and the mention of an optional form filter hints at narrowing behavior. But there is no explicit 'use this when…' or 'use find_provider_hrt_prices instead when…' guidance, and no prerequisites or exclusions are given.

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