Skip to main content
Glama

Compare channels for one model

compare_channels
Read-onlyIdempotent

All channels for a model sorted by input price, with the difference versus the official list price. List prices as published by each channel at observed_at, USD per 1M tokens unless stated; China-site price lists are in CNY, listed separately and never converted. Standard (on-demand) plan unless service_plan says otherwise. The channel's own page is authoritative. Aggregator prices are the marketplace's own and never the reference. A missing price is unknown, not free. Not purchasing advice.

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": {
      "model": "<model>"
    },
    "name": "compare_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesModel id such as openai/gpt-6.1-sol, or an alias the channels use (gpt-6.1-sol, claude-opus-5-5). Case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations only cover safety (readOnly, idempotent, non-destructive, closed-world); the description goes well beyond them with data-provenance rules: currency handling for China-site lists (CNY, never converted), standard on-demand plan default unless service_plan says otherwise, channel page as authoritative source, aggregator prices excluded as reference, and observed_at timestamp for each price. The explicit 'a missing price is unknown, not free' rule prevents a specific, plausible misinterpretation of the result set.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the result definition, then a compact sequence of interpretation rules, one clause each, with no filler. Density is high but appropriate; only 'Not purchasing advice' sits close to boilerplate, and even that forestalls a plausible misuse.

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 one-parameter read tool with annotations covering safety, the main remaining gap is the return shape: with no output schema, the description implies fields (channel, input price, difference versus list price) but never states the comparison basis, ordering ties, or whether every channel is always present. Adequate but not fully self-contained for an agent parsing the response.

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%: the single model parameter documents accepted ids, alias forms, case-insensitivity and length bounds. The description adds only the implicit note that a model is required; no extra syntax or format meaning is contributed beyond the schema, so the baseline 3 applies.

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?

States a concrete result set: all channels for a model, sorted by input price, with the delta versus the official list price. That scope (full multi-channel comparison with a computed difference) is distinguishable from price-lookup siblings such as get_price, check_price or cheapest, though the description never names an alternative.

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?

Usage is implied by the scope rather than stated: an agent can infer this is the multi-channel comparison view, but there is no explicit 'use this when you want X, use cheapest when you want Y' routing. The rules given are about interpreting prices, not about selecting the tool.

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.