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

ai-api-prices

by Liutasil501
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Compare two models on price

compare_models
Read-only

Evaluate two AI models by each model's cheapest provider price and provider counts in USD, with an optional category filter to scope lookups.

Instructions

Compare two AI models in USD by each model's cheapest priced provider (3 input : 1 output blended per 1M tokens for text LLMs, unit rate otherwise) and provider counts. Optional category scopes both model lookups; cross-category pairs display both prices without a price ratio. Use model_prices for every provider of one model or cheapest_models for category lows.

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_a": "<model_a>",
      "model_b": "<model_b>"
    },
    "name": "compare_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_aYesFirst model name or slug, e.g. "gpt-6.1 sol".
model_bYesSecond model name or slug, e.g. "claude opus 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. Changed3 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_a / description
      Previous value: -"First model"New value: +"First model name or slug, e.g. \"gpt-6.1 sol\"."
    • changedInput schema / properties / model_b / description
      Previous value: -"Second model"New value: +"Second model name or slug, e.g. \"claude opus 5.5\"."
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnly and openWorld, so most of the behavioral burden falls on the description, which discloses the exact pricing methodology (3:1 blended per 1M tokens, unit rate otherwise) and that provider counts are returned alongside price. It also reveals the degraded output for cross-category pairs, context the annotations cannot carry. It does not state resolution behavior for ambiguous model names, which keeps it at 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?

Front-loaded with the core action and metric, then the optional-scope caveat, then the sibling routing. Dense but every clause carries information; the parenthetical formula is long but is precisely the detail an agent needs to interpret results.

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 three-parameter read-only tool with no output schema, the description covers the pricing formula, the scoping rule, the cross-category exception, and alternatives, which is enough to call it correctly and interpret the numbers. Only ambiguity handling for model name resolution is unaddressed.

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 baseline is 3, but the description adds real meaning beyond the schema: the optional category scopes both model lookups simultaneously, and cross-category pairs suppress the price ratio. That is behavioral semantics the enum alone does not convey.

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 (compare two AI models in USD) and pins down exactly what is compared: each model's cheapest priced provider, blended 3:1 input/output per 1M tokens for text LLMs, unit rate otherwise, plus provider counts. The final sentence names the siblings it is not (model_prices, cheapest_models), so an agent can distinguish it 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?

Explicit routing is given for both alternatives: use model_prices when you need every provider of one model, and cheapest_models for category lows. It also defines an edge case (cross-category pairs show both prices without a ratio), which tells the agent what this tool will and won't compute before it calls.

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