Skip to main content
Glama
Sign In
ai-api-prices

ai-api-prices

by Liutasil501
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Prices of one model at every provider

model_prices
Read-only

Lists standard USD list prices for one AI model at every priced provider, cheapest first, including input, output, and cached token rates plus pricing page links.

Instructions

List standard USD list prices for one AI model at every priced provider, ordered cheapest first (including size or quality variants for media). Returns input, output, and cached token prices for text LLMs (unit rate otherwise) plus each provider's pricing page URL; unpriced providers are omitted. Use find_models if unsure of the name, compare_models for two models, or estimate_monthly_cost for a monthly bill.

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": "model_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesModel name or slug (best match is selected), e.g. "gpt-oss-120b" or "Claude Sonnet 5.5".
categoryNoOptional category filter: text (LLMs), image, video, transcription (speech-to-text), tts (text-to-speech), search (web search), or embedding.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • changedInput schema / properties / category / description
      Previous value: -"text (LLMs), image, video, transcription, tts, search or embedding"New value: +"Optional category filter: text (LLMs), image, video, transcription (speech-to-text), tts (text-to-speech), search (web search), or embedding."
    • changedInput schema / properties / model / description
      Previous value: -"Model name, e.g. \"gpt-oss-120b\" or \"Claude Sonnet 5.5\""New value: +"Model name or slug (best match is selected), e.g. \"gpt-oss-120b\" or \"Claude Sonnet 5.5\"."
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes further by disclosing result ordering (cheapest first), coverage rules (unpriced providers omitted), media variants included, and the exact payload (input/output/cached token prices or unit rate, plus each provider's pricing page URL). With no output schema, this carries the return-value burden well.

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 front-loaded: the primary behavior and return shape first, then the routing to alternatives. Dense but every clause carries information (ordering, omissions, units, URLs) with no filler.

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?

For a two-parameter read-only lookup with no output schema, the description covers what is returned, how it is ordered, what is excluded, and which sibling to use instead. Nothing an agent needs to call it correctly is missing.

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 coverage is 100%, so both the model and category parameters are already documented in the schema, setting the baseline at 3. The description adds only marginal meaning, implying that media categories surface size/quality variants and that non-text models return a unit rate rather than token prices.

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?

States a specific verb and resource ("List standard USD list prices for one AI model at every priced provider") plus scope, ordering and unit (cheapest first, USD list). An agent can distinguish it from compare_models, find_models and estimate_monthly_cost without opening any schema.

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

Usage Guidelines5/5

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

Explicitly routes three alternatives: find_models when the model name is unknown, compare_models for two models, estimate_monthly_cost for a monthly bill. The implicit when-to-use case (pricing one model across providers) is clear from the opening sentence, leaving little to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools