Skip to main content
Glama

Get a model's prices on every channel

get_price
Read-onlyIdempotent

Latest standard price per channel for one model, each with region, pricing mode, trust status, observation time and source snapshot, plus Batch / Flex / Priority / Ultrafast plan prices where a channel publishes them. List prices as published by each channel at observed_at, USD per 1M tokens unless stated; China-site price lists are in CNY, listed separately and never converted. Standard (on-demand) plan unless service_plan says otherwise. The channel's own page is authoritative. Aggregator prices are the marketplace's own and never the reference. A missing price is unknown, not free. Not purchasing advice.

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

Input Schema

NameRequiredDescriptionDefault
modelYesModel id such as openai/gpt-6.1-sol, or an alias the channels use (gpt-6.1-sol, claude-opus-5-5). Case-insensitive.
channelNoChannel id to restrict to, e.g. azure-datazone-eu, vertex-regional, openrouter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world safety, so the bar is lower; the description still adds substantial context: USD per 1M tokens, CNY for China-site lists and never converted, channel page authoritative over aggregators, and missing price means unknown rather than free. It does not cover freshness/rate limits or the exact response shape beyond the field list, which keeps it at a 4.

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?

Content is front-loaded with the core scope in the first clause, and each following sentence carries a distinct rule (units, currency, plan default, source authority, missing-price semantics). The opening sentence is long and dense, and the authority/aggregator pair could be tightened, but there is little throwaway text.

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?

With no output schema, the description carries the burden and does so: it enumerates the returned fields, currency and unit conventions, default plan, and interpretation rules for missing or aggregator-sourced prices. An agent can call this correctly and read the result without further context.

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; the description goes beyond it by explaining what a channel means in this domain (channel-published list vs aggregator marketplace prices, China-site channels reported in CNY) and by fixing the default plan, adding genuine meaning to the `channel` parameter.

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?

The description states a specific verb+resource+scope: latest standard price per channel for one model, plus plan-tier prices. It enumerates the returned fields (region, pricing mode, trust status, observation time, source snapshot), which clearly separates it from sibling tools like cheapest or compare_channels that aggregate across models or pick winners.

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 implied by the scoping language ('one model', 'per channel', 'standard plan unless service_plan says otherwise'), and the authority rules tell the agent how to interpret results. But there is no explicit when-to-use/when-not guidance and no sibling tool is named as an alternative for comparison or cost estimation.

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.