Skip to main content
Glama

cheapest_offers

Read-only

The cheapest current offers (rows: one model at one provider) of one model type, by input price. For the cheapest MODELS of a job (one row per model) use cheapest_models_by_task; for a monthly workload use cheapest_for_workload.

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

Input Schema

NameRequiredDescriptionDefault
limitNorows, 10 by default
categoryNomodel type, llm (text models) by default

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "llm",
      -  "embedding",
      -  "rerank",
      -  "moderation",
      -  "ocr",
      -  "search",
      -  "image_generation",
      -  "image_editing",
      -  "video_generation",
      -  "text_to_speech",
      -  "speech_to_text",
      -  "speech_to_speech",
      -  "audio_generation",
      -  "3d_generation"
      -]New value: +[
      +  "llm",
      +  "embedding",
      +  "rerank",
      +  "moderation",
      +  "decision",
      +  "ocr",
      +  "search",
      +  "image_generation",
      +  "image_editing",
      +  "video_generation",
      +  "text_to_speech",
      +  "speech_to_text",
      +  "speech_to_speech",
      +  "audio_generation",
      +  "3d_generation"
      +]
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

The description adds significant behavioral context by specifying that the results are based on 'input price' and refer to 'one model at one provider.' While annotations confirm it is a read-only operation, the description provides essential business constraints.

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?

The description is highly concise, fitting all necessary information into two sentences. It front-loads the primary function before presenting the routing logic for specialized use cases.

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 list-type query tool, the definition is complete. It tells the agent exactly what data to fetch (cheapest offers) and provides a clear decision tree (if X use this, if Y use that sibling).

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%, providing a baseline 3. The description reinforces the purpose of the parameters, clarifying that they select the 'model type' and the number of 'rows' to view, adding functional context.

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?

The description clearly identifies the core function (find cheapest offers) and the scope (one model at one provider). Crucially, it differentiates this tool from siblings by detailing specific use case alternatives.

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?

It provides explicit guidance on when to use this tool versus others. It instructs the agent to use 'cheapest_models_by_task' for job-based models and 'cheapest_for_workload' for monthly work, solving routing ambiguity instantly.

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