Skip to main content
Glama

Ezkielyna Public Tools

Model status (uptime, latency, speed)

model_status
Read-onlyIdempotent

Live status of AI models on Ezkielyna, one independent API gateway: success rate (24 h), uptime (7 d / 30 d), time to first token (p50/p90), output speed and request counts. Give "model" for one model, or leave it empty for the top N sorted by uptime, latency (fastest first token), speed (tokens/s) or requests (busiest). Free, no API key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "model_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoHow many models to list.
kindNoOptional family filter as used by the status file: deepseek, gpt, claude, gemini, glm, qwen, kimi, minimax, image, video, audio, other.
modelNoModel id, e.g. deepseek-v4.1-flash or claude-sonnet-5.5. Leave empty for a top-N list.
sort_byNoRanking for the top-N list.uptime
min_requests_7dNoFor sort_by=uptime: ignore models with fewer answers in 7 days (a 100% uptime from 3 requests means little).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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, openWorldHint). The description adds real context beyond that: the data is free with no API key required, and each metric carries an explicit time window (24 h, 7 d, 30 d), which tells the agent how fresh the numbers are. It stops short of describing response shape or rate limits.

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?

Two dense sentences with no filler; the metric inventory comes first and the mode-selection rule second, so the reader gets the scope before the options. The metric list is long but every item is load-bearing.

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 usefully enumerates the returned fields (success rate, uptime, TTFT percentiles, speed, request counts), which is the main thing an agent needs. Free/no-key access is stated. Remaining gaps are minor: no mention of response format, units, or error behavior for an unknown model id.

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 description coverage is 100%, so all five parameters are already documented, and the baseline is 3. The description does add a little meaning by glossing the sort modes as 'fastest first token', 'tokens/s' and 'busiest', but the min_requests_7d rationale and the kind filter values live only in the schema.

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?

States a specific verb and resource ('Live status of AI models on Ezkielyna') and enumerates the exact metrics exposed: success rate over 24 h, uptime over 7 d/30 d, TTFT p50/p90, output speed, request counts. An agent can tell this apart from compare_models or lowest_price_models because the definition frames it as a monitoring/telemetry feed rather than a comparison or pricing tool.

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?

Gives explicit branching guidance: pass 'model' for a single model, leave it empty for a top-N list ranked by uptime, latency, speed, or requests. Clear operating context, though it never names when to prefer a sibling such as compare_models or usage_leaderboard.

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