Skip to main content
Glama

AI Capital Index

get_model_prices

Today's official API list prices (USD per 1M tokens) for leading AI language models from 12 providers, read daily from each provider's pricing page. Free.

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

Input Schema

NameRequiredDescriptionDefault
modelNoFilter by text in the model name
providerNoFilter by provider name, e.g. OpenAI, Anthropic, Google

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses data provenance and freshness ('read daily from each provider's pricing page'), the unit and currency (USD per 1M tokens), the coverage breadth (12 providers), and that access is free. It stops short of describing result shape or limits when no filter is applied, so an agent cannot predict the response size.

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?

A single sentence with no waste, front-loading the resource, currency, and unit before the provenance and cost details. Every clause (freshness, units, provider count, free) earns its place.

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

Completeness3/5

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

For a simple read-only lookup with full parameter documentation, the key interpretive details (currency and per-token unit) are present, which helps since there is no output schema. However, the description never distinguishes this tool from get_price_history and says nothing about default coverage or result structure, leaving meaningful gaps for an agent choosing between the two.

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 both parameters ('model' as name text filter, 'provider' with examples) are fully documented in the schema. The prose adds only corroborating context (12 providers, model names) without extra syntax, matching behavior, or format detail, so the baseline of 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?

The description names a specific resource — today's official API list prices in USD per 1M tokens for AI language models across 12 providers — so an agent knows exactly what data comes back. It does not name or differentiate itself from the sibling get_price_history, leaving the temporal scope ('Today's') as the only implicit distinguisher.

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: 'Today's' signals a current-snapshot tool, which suggests the sibling history tool covers the past, but the description never says when to use one over the other. There are no exclusions, prerequisites, or explicit alternative routing.

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