Skip to main content
Glama

Ask several models the same thing

compare

Sends the same conversation (or one prompt) to 2 to 5 chat model ids at once through POST /v1/chat/completions and returns every answer side by side with its token usage, cost and time, plus the total. For a second opinion from another model, or to pick the model that answers a kind of question best. Completions are capped at max_tokens each (default 1024). Each model is billed to the key in the MCP request's Authorization header; a model that fails is reported and not charged.

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": {
      "models": "<models>"
    },
    "name": "compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelsYes2 to 5 chat model ids from list_models, asked at the same time.
promptNoOne user message, in place of messages.
systemNoInstructions placed ahead of the conversation as a system message.
messagesNoThe conversation, OpenAI chat format.
image_urlsNoImage URLs attached to the last user message, for the chat models that take images (input_modalities in list_models). A file generate made works.
max_tokensNoCap on completion tokens per model. Default 1024.
temperatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses per-model max_tokens capping (default 1024), that each model is billed to the key in the request's Authorization header, and that a failing model is reported and not charged. These are exactly the cost and partial-failure behaviors an agent needs before invoking a non-readOnly, open-world call.

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 action and return shape, then usage framing, then cost/failure behavior. No filler and nothing repeated from the schema verbatim beyond what reinforces the key constraint.

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?

No output schema exists, and the description still explains what comes back (side-by-side answers with tokens, cost, time, plus totals). Combined with cost attribution and partial-failure handling, it covers everything needed to call a 7-parameter tool correctly.

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 86%, so the parameters are already documented. The description reinforces the 2-5 model range and the max_tokens default/cap, but adds little semantic detail not already present in the schema descriptions, so the baseline 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: sends the same conversation or one prompt to 2-5 chat model ids and returns answers side by side with token usage, cost, time and total. It even names the underlying endpoint (POST /v1/chat/completions), which distinguishes it clearly from single-model siblings like chat or generate.

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

Usage Guidelines4/5

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

Gives a clear when-to-use: a second opinion from another model, or picking the model that answers a kind of question best. It does not explicitly state a when-not or route the agent to chat for single-model calls, but the multi-model framing makes the boundary inferable.

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.