Skip to main content
Glama

Find TRT Prices

find_trt_prices
Read-only

Current US self-pay prices of testosterone replacement therapy (TRT) programs from TRT Buyer Guide's dated records, returned in the guide's ranked order (score-based). An optional form filter (injectable, topical 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_trt_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
formNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the records are dated, results come back in the guide's score-based ranked order, and each row carries a source page and check date. It stops short of stating result volume, pagination, or how stale the dated records may be, which matters for a price-lookup tool.

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?

Three sentences, front-loaded with the core resource and scope, then the filter, then the result shape. No filler or repetition, though the parenthetical '(score-based)' is slightly redundant with 'ranked order'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 tool with no output schema, the description covers source, ordering, filter behavior and per-result metadata, which is close to sufficient. Missing are result-set size expectations, empty-result behavior, and any hint of data freshness cadence beyond the per-record check date.

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 coverage is 0%, but with a single optional enum parameter the burden is small. The description does add real meaning by explaining the filter semantics: it keeps only programs whose recorded price covers the chosen form, rather than merely accepting the enum value. That is a meaningful clarification of what the filter actually does.

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 and scope: 'Current US self-pay prices of testosterone replacement therapy (TRT) programs', plus the data source (TRT Buyer Guide) and ordering. It is clear what the tool returns, but it never distinguishes itself from the sibling find_provider_trt_prices, which on name alone appears to cover a related but different price surface.

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 or when-not-to-use guidance, and no alternative is named. An agent can infer that this tool is for program-level self-pay pricing, but nothing tells it whether to prefer find_provider_trt_prices or list_trt_treatments in any given situation.

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