Skip to main content
Glama

compare_models

对比指定模型:上下文长度、类型、输入/输出单价。传入 2–6 个模型标识。

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": {
      "codes": "<codes>"
    },
    "name": "compare_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
codesYes模型标识列表,如 ["claude-sonnet-5-5","gpt-6-sol"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the full disclosure burden, and it does tell the agent which attributes will be compared (context length, type, input/output pricing). It omits error behavior for unknown codes and does not state where valid identifiers come from (presumably list_models).

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 with zero filler; the comparison scope is front-loaded before the input constraint. Nothing is repeated from the schema beyond the essential cardinality hint.

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 single-parameter read comparison with no output schema, the description adequately conveys what is returned and how many inputs to supply. The main remaining gap is not pointing to list_models as the source of valid identifiers, but that is a minor omission for a tool this simple.

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

Parameters4/5

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

Schema coverage is 100%, so the single `codes` array is already documented with an example, setting the baseline at 3. The description adds the 2–6 element range, a constraint the schema does not encode via minItems/maxItems, which is real value beyond the structured field.

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 (compare) and resource (models) and enumerates the compared facets: context length, type, and input/output unit price. This makes the tool distinguishable in spirit from list_models and call_model, though it never names those siblings explicitly.

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?

The phrase "Pass in 2–6 model identifiers" gives a concrete cardinality constraint for invoking the tool, which is genuine usage guidance. However, it never says when to prefer compare_models over list_models or call_model, nor what happens if fewer than 2 codes are supplied.

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.