Skip to main content
Glama

Voicedex

compare_models

Read-onlyIdempotent

Compare up to 6 models side by side. Each item can be an exact key "provider/type/model_id" (from search_models) or a loose name like "deepgram nova-3" or "Cartesia Sonic 3". A loose name resolves to the best match and says so in matched_as (with other_candidates): tell the user what was assumed. Unmatched items come back with "did you mean" suggestions when something is close.

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

Input Schema

NameRequiredDescriptionDefault
modelsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, it discloses automatic best-match resolution for loose names, the matched_as and other_candidates transparency fields, and did-you-mean suggestions for close unmatched items. These details explain important ambiguity and failure behavior rather than merely restating the annotations.

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 purpose and item limit are front-loaded, followed by input formats, resolution behavior, and unmatched-item handling in a logical order. Every sentence contributes actionable information without unnecessary background or repetition.

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 single-parameter comparison tool, the definition covers scope, accepted inputs, ambiguity handling, and agent-facing follow-up behavior. The existing output schema reduces the need for further return-value documentation, and nothing essential to making a valid call is conspicuously absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description substantially compensates by documenting the six-item limit, the provider/type/model_id exact-key format, loose-name support, and concrete examples. It gives the sole models parameter enough meaning for correct invocation.

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 opening sentence gives a specific operation, resource, and scope: comparing up to six models side by side. It references search_models as a source of exact keys, but does not explicitly distinguish this tool from siblings such as get_model or find_alternatives.

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?

The description supplies a clear workflow: exact keys can come from search_models, loose names are acceptable, and the agent should disclose any assumed resolution to the user. It does not provide explicit when-not guidance or route comparison needs to alternative siblings.

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.