Skip to main content
Glama

MenoCost.com: US menopause care prices

Treatments with prices

list_menopause_treatments
Read-onlyIdempotent

Every menopause treatment this site keeps a price list for, with its lowest 30-day cost, how many prices it has and its page.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, closed-world, idempotent, and non-destructive, so the safety profile is handled elsewhere. The description adds genuinely useful return-shape context (cost basis is the lowest 30-day price, plus a price count and page reference), but says nothing about ordering, result size, or whether the list is bounded.

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 sentence with no filler, front-loaded on the resource and then the per-entry fields. The trailing clause 'how many prices it has and its page' is slightly compressed to the point of ambiguity (count of what, page of what), which keeps it off a 5.

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 and no parameters, the description carries the return-value burden, and it does name the key fields an agent would need. What's missing is minor: ordering, cardinality, and the meaning of 'page'. Adequate for a simple zero-argument catalog listing.

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?

The tool takes zero parameters, so the baseline applies and no parameter explanation is owed. The description instead spends its words on output semantics, which is the right allocation.

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 (menopause treatments with a price list) and enumerates exactly what each entry carries: lowest 30-day cost, price count, and page. That is well beyond a restatement of the name/title. It stops short of 5 because it never distinguishes itself from the sibling find_menopause_treatment_prices, so an agent must infer the list-vs-lookup split.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement, no prerequisites, and no mention of alternatives such as the find_* price tools. The phrase 'every menopause treatment this site keeps a price list for' implicitly signals a complete, unfiltered catalog browse, which is a weak usage cue but isn't framed as guidance for choosing between tools.

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