Skip to main content
Glama

Compare prices

get_prices
Read-onlyIdempotent

Published prices side by side, cheapest first: model tokens per million, or per unit (1k-requests, 1k-pages, …) for a capability. Use it when a user asks what something costs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoA unit such as 1k-requests or 1k-pages; empty for model tokens
limitNoHow many rows to return, cheapest first (default 40); the result says how many there are
categoryNoOnly listings in this category, e.g. search; works like capability
capabilityNoOnly listings with this capability, e.g. web.search; without unit, the cheapest in every unit it's priced in
maxBlendedNoModels only: at most this many dollars blended per million tokens

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / capability
      Added value: +{
      +  "description": "Only listings with this capability, e.g. web.search; without unit, the cheapest in every unit it's priced in",
      +  "type": "string"
      +}
    • addedInput schema / properties / category
      Added value: +{
      +  "description": "Only listings in this category, e.g. search; works like capability",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "How many rows to return, cheapest first (default 40); the result says how many there are",
      +  "maximum": 300,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral detail beyond them: results are sorted cheapest-first, and the response reports how many rows exist total (implying truncation via limit).

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?

Two sentences, both load-bearing: the first establishes what is returned and the ordering, the second establishes the trigger. No filler, and the output shape is front-loaded.

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?

For a read-only filtered listing tool with all five parameters documented and no output schema, this is close to sufficient — the ordering and the total-count hint cover the main return-value question. Missing only a note on how the five filters combine (e.g. capability without unit) in the description itself, though the schema covers that.

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

Parameters3/5

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

Schema description coverage is 100% and each of the five parameters is documented (unit, limit, category, capability, maxBlended). The description's mention of tokens-per-million versus per-unit pricing adds a bit of framing for the unit parameter, but largely restates what the schema already explains, so the baseline 3 applies.

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?

"Published prices side by side, cheapest first" states the resource (published prices) and the output ordering, plus the two pricing modes (per million tokens vs. per unit such as 1k-requests). It is clear what the tool returns, though it never distinguishes itself by name from the sibling compare_tools.

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?

"Use it when a user asks what something costs" gives a usable trigger condition, which is better than nothing. But there are no exclusions and no routing advice toward compare_tools or search_tools, so the agent must infer which of the price/comparison tools is right for a given request.

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