Skip to main content
Glama

Find Provider HRT Prices

find_provider_hrt_prices
Read-only

Every recorded HRT price from one provider in HRT 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_hrt_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerYes

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 fully covered. The description adds value by disclosing what comes back (source page and check date, i.e. provenance and freshness), but says nothing about result volume, truncation, or what an empty result means for a tool claiming 'every recorded price.'

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?

One front-loaded sentence with no filler; scope and returned fields come first. It is efficient, though its brevity is partly the source of the missing parameter and volume guidance rather than pure conciseness.

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 simple single-parameter read-only tool backed by annotations and with no output schema, the description covers purpose and returned fields adequately. It is still incomplete on the provider identifier format, matching behavior, and result size limits, which matter because the tool promises 'every recorded' price.

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' parameter, so the schema supplies no meaning at all. The description only says prices come 'from one provider' and never clarifies whether the string should be a provider name, an ID, or how matching works (exact vs partial), leaving the one input genuinely ambiguous.

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 the resource (recorded HRT prices), the scope (a single provider), and the returned fields (source page and check date), so an agent knows this is a provider-scoped price lookup. It stops short of explicitly contrasting itself with a general price-lookup sibling, leaving the distinction implicit in the 'one provider' scoping.

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 only implied: the 'from one provider' framing suggests calling it when a specific provider is known, but there is no explicit when-to-use statement, no exclusions, and no mention of how it relates to other price-finding tools. An agent must infer the selection condition.

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