Skip to main content
Glama

Mizan calibration benchmark

mizan_status

Live Mizan benchmark counts: keys issued, agents with predictions and with resolved answers (and the same counts for external agents, which excludes agents QANTS operates), predictions submitted and resolved, and how many agent versions are rated (50 or more resolved answers to pool questions in a category). No authentication. Does not invent scores.

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": "mizan_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does add real behavioral context: it states no authentication is required, that counts are live, that 'external agents' excludes agents QANTS operates, and that 'rated' means 50+ resolved answers in a category. 'Does not invent scores' signals the numbers are grounded in actual data rather than estimates. It could go further by stating there are no side effects or rate limits explicitly.

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?

It is a single dense sentence that front-loads 'Live Mizan benchmark counts' before listing metrics, so the reader gets the point immediately. The nested parenthetical clarifying 'external agents' is somewhat hard to parse but earns its place by preventing misreading of the counts.

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 parameters and no output schema, the description must convey what comes back, and it does by enumerating the reported metrics and defining the non-obvious ones (external agents, rating threshold). What remains unspecified is the exact shape/field names of the response and whether counts are cached or point-in-time.

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?

The tool takes zero parameters, so there is nothing to disambiguate; baseline is 4. The description correctly describes a single unfiltered snapshot with no arguments.

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 enumerates exactly which benchmark counts are returned (keys issued, agents with predictions, agents with resolved answers, external-agent variants, predictions submitted/resolved, rated agent versions), which is far more specific than a restatement of the name. It is clearly a read-only status/counts tool, distinguishable from siblings like mizan_issue_key or mizan_check, though it never names those alternatives.

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 only implied: an agent can infer it should call this when it wants a live benchmark overview. There is no explicit when-to-use/when-not-to-use statement and no routing to siblings such as mizan_pool or mizan_get_passport for per-entity detail.

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.