Skip to main content
Glama

Cheapest models for a workload

cheapest_models_for
Read-only

Rank models by monthly cost for a workload. Use a preset (chatbot, rag, coding_agent, research_agent) or give token numbers.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return (default 5, max 20)
presetNoOptional workload preset that fills in token defaults: chatbot, rag, coding_agent, research_agent. Explicit numbers override it.
input_tokensNoInput tokens per call/step
popular_onlyNoOnly well-known models (default true)
calls_per_dayNoCalls (or agent tasks) per day
output_tokensNoOutput tokens per call/step
cached_percentNoShare of input billed at the cached price, 0-100 (default 50 if steps_per_task>1, else 0)
steps_per_taskNoModel calls per task for multi-step agents (default 1)
reasoning_ratioNoHidden reasoning tokens per output token, billed at the output price, on reasoning-capable models only (default: the preset's value, 0.9 for agent presets and custom workloads, 0 for chatbot; 0 excludes reasoning)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / reasoning_ratio
      Added value: +{
      +  "description": "Hidden reasoning tokens per output token, billed at the output price, on reasoning-capable models only (default: the preset's value, 0.9 for agent presets and custom workloads, 0 for chatbot; 0 excludes reasoning)",
      +  "type": "number"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint and openWorldHint=false, so the safety profile is covered. The description adds that presets fill in token defaults and that explicit numbers override them, which is useful behavioral context, but says nothing about how the ranking is computed, sort order, or whether costs are estimates versus billed prices.

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 short sentences, front-loaded with the core action and then the input alternatives. Every clause carries weight and there is no filler or repetition.

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 9-parameter tool with conditional defaults and no output schema, the description is thin: it never sketches what a ranked result contains (cost figure, assumptions used, reasoning applied) or which defaults take effect when called with no arguments. The rich schema compensates for the parameter side, but the output shape is left entirely to inference.

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%, so the baseline is 3. The description only restates the preset-vs-explicit-numbers relationship that the schema already documents ('Explicit numbers override it'), and adds no meaning for the nine parameters, including the conditionally-defaulted cached_percent and reasoning_ratio.

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 states a specific verb and resource: 'Rank models by monthly cost for a workload.' It is clear about what is produced (a ranking) and the axis (monthly cost), but it never distinguishes this from siblings like estimate_cost or compare_models, leaving the agent to infer the boundary.

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?

It gives two usage modes — 'use a preset ... or give token numbers' — which implies the caller should pick one path. However, there is no explicit when-to-use versus estimate_cost/compare_models, no statement about what happens with zero arguments (all params are optional), and no exclusion guidance.

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.