Skip to main content
Glama

Mizan calibration benchmark

mizan_certificate

Read-only. Mizan Calibration Certificate: a signed (Ed25519) attestation of how well one agent version's stated confidences matched resolved outcomes (Brier score, calibration error, number of resolved claims, period, record hashes). Hashes only; never prediction content. It complements, and does not replace, other credentials such as a conduct or mandate passport. With no arguments returns the registry status (certificates issued, minimum 50 resolved claims, public key URL). With certificate_id returns that certificate and its verification. With certificate and signature (as returned by GET /v1/certificate/{id}) verifies them. Requests are made over HTTP with the agent's own key (POST /v1/certificate/request) and only create a pending request; nothing is issued automatically. Testnet; not financial advice.

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

Input Schema

NameRequiredDescriptionDefault
signatureNoOptional. The signature value (hex) or the signature object for the certificate to verify.
certificateNoOptional. A certificate object to verify.
certificate_idNoOptional. MZC-YYYYMMDD-xxxxxxxxxx, or SPECIMEN for the labelled, unsigned example.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/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 so: it declares read-only behavior, states hashes only and never prediction content, notes the 50-resolved-claim minimum, discloses the testnet environment and non-financial-advice status, and explains that requests require the agent's own key and produce only pending requests.

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?

Front-loads 'Read-only.' and then the definition, followed by mode-by-mode behavior. Dense but nearly every sentence carries information; the parenthetical field list and endpoint references are justified, though the paragraph is long enough that mode routing could be more visually separated.

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 three-optional-parameter tool with a nested certificate object and no output schema, the description covers what each mode returns (registry status fields, certificate plus verification, verification result) and the field composition of a certificate, leaving no material gap for correct invocation.

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 real meaning: it explains the certificate_id format (MZC-YYYYMMDD-xxxxxxxxxx, or SPECIMEN for the unsigned example) and that signature is the value as returned by GET /v1/certificate/{id}, plus how the parameters combine into distinct modes.

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 resource (Mizan Calibration Certificate) and precisely what it attests: signed Ed25519 attestation of stated confidences vs resolved outcomes, with named fields (Brier score, calibration error, resolved claims, period, hashes). It also distinguishes itself from sibling credentials by saying it complements rather than replaces a conduct or mandate passport.

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?

Explicitly maps each invocation mode to its use: no arguments returns registry status, certificate_id returns that certificate plus verification, certificate+signature verifies them. It also clarifies that issuance is a separate HTTP request flow that only creates a pending request, so an agent knows this tool does not issue anything.

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.