Skip to main content
Glama

Mizan calibration benchmark

mizan_pool

Read-only. List today's fixed public Mizan question pool (5 yes/no questions a day, each resolving 24 to 72 hours after it opens), with each question_id, text, resolution source and rule, and the day's SHA-256. No authentication, no side effects. Answer a pool question with mizan_check using its question_id (answer yes, no or IDK, confidence 0 to 1). Only pool answers count toward a rating. Optional day (YYYY-MM-DD, GMT+2) reads one published day; manifest=true lists every day's SHA-256.

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_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoOptional YYYY-MM-DD (GMT+2). Omit for today's pool.
manifestNoSet true to list the SHA-256 manifest of all filed pool days instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and does well: it declares read-only behavior, no authentication, and no side effects, plus the 24-to-72-hour resolution window and rating relevance. It does not discuss rate limits or error behavior, which keeps it short of fully exhaustive.

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?

The description is dense and front-loaded, starting with read-only and the pool-listing purpose before moving into operational details. Every sentence adds useful context, and there is no unnecessary wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, read-only tool with no output schema, the description is complete enough to call it correctly. It explains the return fields, authentication and side-effect posture, resolution timing, day and manifest behavior, and how answering relates to mizan_check.

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%, so both day and manifest are already documented in the schema. The description adds modest context about reading a published day and listing every day's SHA-256, but largely restates the schema's meaning, so the baseline score of 3 is appropriate.

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 states a specific verb and resource: it lists today's fixed public Mizan question pool, including the number of questions, resolution window, and returned fields. It also distinguishes the tool from mizan_check by explaining that pool questions are answered with mizan_check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes answering to mizan_check using a question_id and clarifies that only pool answers count toward a rating. It also explains that day reads one published day while manifest=true lists every day's SHA-256, giving clear usage context for both parameters.

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.