Skip to main content
Glama

Ezkielyna Public Tools

Compare models (price, latency, uptime)

compare_models
Read-onlyIdempotent

Side-by-side comparison of 2-6 AI models on Ezkielyna: list price per 1M input/output tokens in USD with approximate IDR (or price per image/second/request for media models), key group, time to first token p50/p90, output speed, success rate 24 h and uptime 7 d / 30 d. Prices are this one gateway's list prices, not a market survey. Free, no API key.

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
modelsYesModel ids, e.g. ["deepseek-v4.1-flash", "gpt-6-luna", "claude-haiku-5-5"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world, so the bar is lower. The description still adds real context annotations cannot express: the call is free, requires no API key, the price figures are this gateway's list prices and not market data, and the freshness windows behind success rate (24 h) and uptime (7 d / 30 d).

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?

One dense sentence front-loads the purpose and then the returned metrics, plus a short caveat sentence. Nothing is redundant with the title or annotations, though the metric enumeration is packed enough that an agent must parse carefully.

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?

With no output schema, the description carries the return-value burden and does so by listing every metric plus currency handling and the list-price caveat. Minor gaps remain: no mention of result ordering, of what happens with an unknown or duplicate model id, or of response size for the maximum of six models.

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% and the single parameter carries its own example list of model ids, so the schema already does the work. The description's "2-6" phrasing echoes minItems/maxItems and its media-model note hints that image/second/request pricing applies to non-text models, but it adds little semantic detail about id format or behavior on unknown ids.

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?

Names a specific verb and resource ("Side-by-side comparison of 2-6 AI models") and then enumerates exactly which attributes come back — price per 1M tokens with IDR approximation, TTFT p50/p90, output speed, success rate, uptime windows. This is far more than a restatement of the name and lets an agent distinguish it from lowest_price_models or model_status without opening the schema.

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 2-6 model bound and the statement that prices are one gateway's list prices rather than a market survey imply a comparison-in-context use case. However, no sibling is named and there is no explicit when-to-use or when-not-to-use guidance versus lowest_price_models or model_status, so the agent must infer routing.

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