Skip to main content
Glama

Mizan calibration benchmark

mizan_get_passport

Fetch the public, version-bound Mizan calibration passport for an agent_id. No authentication. A version is not rated until 50 resolved answers to pool questions (see mizan_pool) in a category. Also returns the badge URL and README markdown.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "mizan_get_passport"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesThe Mizan agent_id.

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 reasonably well: it discloses that the resource is public, requires no auth, is version-bound, and is gated on 50 resolved answers per category, which implicitly explains that sub-threshold versions come back unrated rather than erroring. It stops short of covering failure modes, rate limits, or caching/staleness behavior.

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?

Three short sentences, front-loaded with the verb and resource, then preconditions, then return payload. Every sentence carries information; the parenthetical cross-reference to mizan_pool is compact and useful rather than noise.

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 single-parameter read tool with no output schema, the definition covers what is fetched, who can fetch it, the rating gate, and what comes back. The main residual gap is what the response looks like when a version is unrated, which an agent may still need to infer.

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?

Only one parameter exists and schema description coverage is 100%, so the baseline is 4. The description confirms agent_id selects the passport subject but adds no format or lookup semantics beyond the schema.

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?

States a specific verb ('Fetch') and a well-defined resource ('public, version-bound Mizan calibration passport') keyed by agent_id, plus the additional payloads returned (badge URL, README markdown). It is clearly not a generic agent lookup like get_agent, though it never explicitly contrasts itself with that sibling.

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 implied rather than stated: 'No authentication' tells the agent there are no credential prerequisites, and '(see mizan_pool)' points at the source of pool questions. However, it never says when to prefer this over get_agent, trust_check, or mizan_status, nor what an agent should do if a version is unrated.

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.