Skip to main content
Glama

List TRT Treatments

list_trt_treatments
Read-only

Testosterone treatment forms TRT Buyer Guide holds priced program records for, with counts of priced programs per form.

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_trt_treatments"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 new information beyond them by stating that each result carries a count of priced programs per form. It stops short of describing ordering, what a 'form' record contains, or whether unpriced forms are excluded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no filler, which is good, but the grammar is tangled ('forms ... holds priced program records for'), which slows comprehension of an otherwise simple concept. The output content (counts) is mentioned almost as an afterthought rather than front-loaded.

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 zero-parameter read-only list call this is close to sufficient, and the annotations cover safety. But with no output schema, the description is the only source of return-value information, and it does not say what fields identify a form (name, id?) or how the list is ordered.

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 there is nothing for the description to disambiguate; the baseline of 4 applies. Schema coverage is 100% and the empty object schema is unambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys that the tool returns testosterone treatment forms plus a count of priced programs per form, so the resource and return content are inferable. However, the verb is only implied (coming from the name/title) and the phrasing 'forms TRT Buyer Guide holds priced program records for' is convoluted, forcing re-parsing. It also never contrasts itself with the price-finding siblings.

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 when-to-use guidance, no exclusions, and no mention of the sibling tools find_provider_trt_prices or find_trt_prices. An agent must infer that this is the enumeration/overview call and the siblings are the filtered price lookups.

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