Skip to main content
Glama

Get current price

get_price
Read-onlyIdempotent

Current list price of one SKU (id like vps/ovhcloud/vps-2027-model2 or llm/official/anthropic/claude-sonnet-5-5) with all secondary prices, USD/EUR equivalents, spec, source URL, verified_at, a stale flag that is true when the source's latest fetch failed (the price shown is then the last verified one), other listings of the same model, and headline_commit where the provider headlines a commitment price (a labelled secondary price; the primary price has no commitment). Returns an error object for an unknown id.

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": {
      "sku_id": "<sku_id>"
    },
    "name": "get_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
sku_idYesSKU id as returned by search_skus, e.g. vps/ovhcloud/vps-2027-model2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

It goes well beyond the annotations, which only cover read-only/idempotent/non-destructive semantics. It explains the stale flag (true when the latest source fetch failed, and that the price then is the last verified one), the headline_commit field (provider-headlined commitment price, a labelled secondary price; the primary has no commitment), and that an unknown id yields an error object.

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?

It is a single front-loaded sentence that leads with the core purpose and then enumerates the returned fields. The list is long and clause-heavy, but since there is no output schema, most of that enumeration carries real information instead of being padding.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required parameter, read-only), and the description covers the return payload in detail, including currency equivalents, verification timestamp, staleness handling, alternate listings, and the error case. Nothing an agent needs in order to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds value by showing two valid id shapes ('vps/ovhcloud/...' and 'llm/official/anthropic/...'), which tells an agent the id is a path-like namespace rather than an opaque token. It does not cover whether the id is case-sensitive or how to handle malformed ids.

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

Purpose5/5

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

It names a specific verb and resource: 'Current list price of one SKU', and gives two concrete id examples in different namespaces (vps/ovhcloud/vps-2027-model2 and llm/official/anthropic/claude-sonnet-5-5). That makes it distinguishable from the sibling search_skus, which returns ids rather than prices.

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 single-SKU framing suggests this tool is for looking up a price once an id is known, and the schema points at search_skus as the way to obtain that id. The description itself never states when to prefer this over get_history, changes_since, or cheapest_for_spec, and it offers no explicit exclusions.

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