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

ai-api-prices

by Liutasil501
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Cheapest models in a category

cheapest_models
Read-only

Find low-cost AI models by category, ranked by provider price in USD, with optional result limits and only priced options included.

Instructions

List the cheapest AI models in a category in USD ranked by lowest provider price, returning up to limit models (default 10). Only priced models appear; text LLMs require at least two priced providers so one-off listings do not crowd the ranking. Use find_models to search by name or model_prices to inspect every provider for one model.

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": {
      "category": "<category>"
    },
    "name": "cheapest_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of models to return, from 1 to 25 (default 10).
categoryYesRequired category: 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, image, video, transcription, tts, search or embedding"New value: +"Required category: text (LLMs), image, video, transcription (speech-to-text), tts (text-to-speech), search (web search), or embedding."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of models to return, from 1 to 25 (default 10)."
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds real behavioral rules: only priced models appear, and text LLMs need at least two priced providers to avoid one-off listings crowding the ranking. It does not describe the returned fields or tie-breaking, but the inclusion rules are the substantive extra context.

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?

Three sentences, front-loaded with the core purpose and ranking semantics, then inclusion rules, then sibling routing. No redundant restatement of the title or schema.

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 two-parameter filtered-list tool with no output schema, the description covers what is ranked, how, in what currency, what is excluded, and where to go instead. Only minor gaps remain, such as tie handling or the shape of each returned entry.

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% and both parameters are fully documented in the schema, including the enum categories and the 1-25 limit range with default 10. The description adds ranking/currency context but no new syntax or format detail beyond what the schema already supplies, so baseline 3 applies.

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 the cheapest AI models in a category'), plus the ranking basis (lowest provider price), currency (USD), and result cap. This is clearly distinguishable from find_models (name search) and model_prices (per-model provider inspection).

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 the agent: use find_models to search by name, model_prices to inspect every provider for one model. The condition selecting each alternative is stated, leaving nothing 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