Skip to main content
Glama

Is this price fair?

check_price
Read-onlyIdempotent

Places a price someone pays or was quoted among the prices on record. For a model API: where it stands against the official list price, the lowest recorded channel and the batch price. For a GPU: how many providers' on-demand list prices it undercuts, and the spot, reserved and marketplace prices. Use it for "is $X a good price for Y". Nothing is stored.

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": {
      "kind": "<kind>",
      "item": "<item>",
      "price": "<price>"
    },
    "name": "check_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesModel id or alias (token), or GPU id such as h100 (gpu)
kindYes
termNogpu only; default ON_DEMAND
priceYestoken: input price in USD per 1M tokens; gpu: price per GPU-hour
currencyNogpu only; CNY compares with mainland China prices
output_priceNotoken only: output price in USD per 1M tokens

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and "Nothing is stored" restates that safety profile rather than extending it. The useful addition is behavioral scope of the comparison itself: what reference points are used for tokens versus GPUs. It says nothing about failure modes (unknown item id, out-of-range price) or how results are shaped, which annotations do not cover.

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?

Three sentences, front-loaded with the core action, then the two mode-specific behaviours, then the trigger phrase and the no-storage note. Every sentence carries content, though the first sentence's phrasing ("a price someone pays or was quoted") is more roundabout than needed.

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?

With no output schema, the description does the work of telling the agent what the comparison reports for each mode, which is the key missing piece. For a 6-parameter read-only lookup it is largely sufficient; only error behaviour and result framing are left implicit.

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 83%, so the baseline is 3, and the description earns a bump by clarifying that the two kind values drive different comparison sets and by surfacing the price concepts (list, lowest channel, batch; spot, reserved, marketplace) that correspond to the term parameter. It does not clarify currency or output_price semantics beyond what the schema already states.

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 uses a concrete framing ("places a price ... among the prices on record") and then splits it into two explicit modes, model API vs GPU, naming the reference points each compares against. That is enough to separate it from siblings like get_price or cheapest, which merely retrieve rather than benchmark a supplied price. The opening sentence is a little abstract, but the two mode sentences make the operation unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives a direct trigger phrase, "Use it for 'is $X a good price for Y'", which tells the agent exactly the user intent that should route here. No exclusions or named alternatives are offered (e.g., when to prefer get_price or compare_channels instead), so it stops short of full routing guidance.

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.