Skip to main content
Glama

Ezkielyna Public Tools

Lowest listed prices on Ezkielyna

lowest_price_models
Read-onlyIdempotent

Models with the lowest listed price on Ezkielyna for a task: chat, coding (models that also work with Claude Code / Codex / OpenCode style agents), image (price per image) or tts (price per 1M characters). Shows uptime next to each price and by default leaves out models whose 7-day uptime is below 90%. Only covers this one gateway, not a market-wide price comparison. 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": {
      "task": "<task>"
    },
    "name": "lowest_price_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoHow many models to list.
taskYesWhat the model is for.
min_uptime_7dNoLeave out models whose known 7-day uptime is below this. Models without status data are kept and marked.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower, yet the description still adds real behavior: prices are shown alongside uptime, sub-90% uptime models are silently excluded by default, and the data is scoped to one gateway rather than market-wide. 'Free, no API key' is useful preconditions context. It stops short of describing ordering ties or result shape beyond price/uptime.

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 sentences, front-loaded with the core offering and the task scope, followed by the behavioral caveats and the scope limitation. Every clause carries information the agent needs; nothing is repeated from the schema or annotations.

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 read-only listing tool with three fully described parameters and no output schema, the description covers units, defaults, filtering behavior, and scope. Minor residual gaps (exact tie-breaking or how 'marked' models appear in results) are handled by the schema note on min_uptime_7d.

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 baseline is 3, but the description adds interpretation the enum alone does not give: 'coding' is glossed as models compatible with Claude Code / Codex / OpenCode style agents, 'image' is priced per image, and 'tts' per 1M characters. That resolves unit ambiguity an agent would otherwise have to guess at.

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?

The description names a specific resource (models) and a specific ranking (lowest listed price) on a specific gateway, then enumerates the four task dimensions the price applies to. The line 'Only covers this one gateway, not a market-wide price comparison' implicitly draws the boundary against the compare_models sibling, so the agent can route without opening either schema.

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?

It states the selection context (for a task: chat, coding, image, tts) and discloses the default behavior of dropping models under 90% 7-day uptime, which materially changes what comes back. It does not explicitly name an alternative such as compare_models or say when not to use this, so it falls short of a full when/when-not statement.

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