Skip to main content
Glama

Read website reference prices

get_reference_prices
Read-onlyIdempotent

Read reviewed Claude website reference prices in their original currency. These have no country, ranking, exchange conversion or purchase eligibility guarantee. Unverified currencies are never returned.

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": {
      "product": "<product>"
    },
    "name": "get_reference_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYes

Output Schema

NameRequiredDescriptionDefault
quotesYes
quoteScopeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description's job is to add data-quality context — and it does: prices are 'reviewed', carry no ranking/conversion/eligibility guarantee, and records with unverified currencies are suppressed. That last point is a real disclosure about result filtering that no annotation conveys.

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

Conciseness5/5

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

Three short sentences, no redundancy, and the positive statement of what is returned comes first with caveats after. Every clause carries distinct information.

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?

An output schema exists, so return shape need not be described, and the definition supplies the caveats an agent needs to avoid over-trusting the values. What is missing is freshness/currency-of-data context and explicit routing to sibling tools for country or converted pricing.

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?

There is a single parameter constrained by a const value ('claude'), so the schema is effectively self-documenting despite 0% description coverage. The description adds no parameter detail, but none is genuinely needed here.

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?

States a specific verb ('Read') and a specific resource ('reviewed Claude website reference prices in their original currency'), which is enough to separate it from a region-price or comparison tool. It stops short of naming a sibling, so the differentiation is inferred from phrasing rather than stated.

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?

The caveat sentence ('no country, ranking, exchange conversion or purchase eligibility') implicitly signals this is the wrong tool when country-level or conversion-aware pricing is needed, but no alternative tool is named and there is no explicit when-to-use or when-not-to-use framing.

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.