Skip to main content
Glama

Find Provider TRT Prices

find_provider_trt_prices
Read-only

Every recorded TRT price from one provider in TRT Buyer Guide's records, with source page and check date.

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": {
      "provider": "<provider>"
    },
    "name": "find_provider_trt_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerYes

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, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral information: it enumerates the returned fields (source page and check date), which annotations cannot convey. It says nothing about result volume, ordering, or what happens when no prices exist for the provider.

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 front-loaded sentence with no redundant wording; the scope (one provider) and the return fields are both stated up front. It is tight, though the compression contributes to some ambiguity about the provider identifier.

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?

With no output schema and no annotations about return behavior, the description is the only source of return-shape information, and it names the fields but not the record structure or completeness guarantees. For a one-parameter read tool it is roughly adequate, but the provider identifier format and empty-result behavior are unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required 'provider' string, so the description carries the full burden. 'from one provider' implies the parameter selects a provider but does not say whether it is a name, an ID, a URL, or a slug, nor what matching rules apply.

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 states a specific resource (every recorded TRT price for a single provider) and its provenance fields (source page and check date), which implicitly distinguishes it from the broader find_trt_prices sibling that presumably spans multiple providers. It stops short of an explicit verb/scope contrast with siblings, so a 4 rather than 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 Guidelines2/5

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

There is no statement of when to use this tool versus find_trt_prices or list_trt_treatments, and no prerequisites or exclusions. The phrase 'one provider' hints at a single-provider scope but the agent must infer the routing decision entirely.

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