Skip to main content
Glama

Get model price

get_model_price
Read-only

API list price of one model (input, output, cached input per 1M tokens) plus example monthly agent costs. For retired models, rates are last recorded list prices (see pricing_basis/recorded_note).

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_model_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesModel id like anthropic/claude-sonnet-5.5, or a name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine value by disclosing that retired models return last recorded list prices and that pricing_basis/recorded_note explain provenance — a real behavioral caveat. It does not cover name-matching behavior or what happens when a model is unknown.

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 tight sentences: the return contents come first, then the caveat about retired models. No filler, no restatement of the title, and the parenthetical packs unit and field detail efficiently.

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?

No output schema exists, so the description carries the burden of describing returns — which it does (three price dimensions, unit basis, example monthly costs, provenance fields). Minor gaps remain around fuzzy name resolution and failure behavior, but the tool is simple enough that this is nearly complete.

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?

With one parameter at 100% schema coverage, the schema already defines 'model' with an example id format; the description adds no per-parameter detail beyond that. Baseline 3 applies since the schema does the work, with slight credit for clarifying that prices are per 1M tokens (unit context for the identifier's meaning).

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?

Names a specific verb+resource ('API list price of one model') and enumerates the returned price dimensions (input, output, cached input per 1M tokens) plus example monthly agent costs. The 'one model' framing implicitly separates it from compare_models and list_models, but no sibling is named explicitly.

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: fetch this when you need a single model's rates. There is no explicit when-to-use/when-not guidance and no routing to siblings like estimate_cost (for workload math) or compare_models (for side-by-side), even though the 'example monthly agent costs' clause overlaps with estimate_cost's territory.

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.