Skip to main content
Glama

Mizan calibration benchmark

mizan_issue_key

Call the public POST /v1/keys endpoint and return a new API key (shown once). The key can only submit checks for this agent_id. First request claims the name. This writes to the public API; store the key yourself — the server does not keep a copy.

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

Input Schema

NameRequiredDescriptionDefault
labelNoOptional short label for this key.
agent_idYes3-80 characters: letters, digits and . _ : @ -
utm_sourceNoOptional. Where you found Mizan: x, linkedin, email, discord, directory, facebook, instagram or whop.
utm_campaignNoOptional. Campaign tag from the link you followed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 well: it discloses that this writes to the public API, that the key is shown only once, that the server keeps no copy, and that scope is limited to checks for this agent_id. Gaps remain on auth requirements, rate limits, and what happens if the name is already claimed.

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?

Four short sentences, front-loaded with the endpoint and return value, and every sentence adds operational information. "First request claims the name" is slightly ambiguous in isolation but is not wasted space.

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?

No output schema exists, and the description compensates by stating that a key is returned and shown once. For a four-parameter creation tool with no annotations, the remaining unstated items (auth, failure modes on duplicate claims) are modest rather than crippling.

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; the description goes slightly beyond by explaining the consequence of agent_id (the key can only submit checks for that agent) and by clarifying that the first request claims the name. The label and utm_* parameters are left entirely to 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?

Names a specific verb and resource ("Call the public POST /v1/keys endpoint and return a new API key") scoped to an agent_id, which an agent can tell apart from check/certificate/status siblings. It stops short of explicitly differentiating itself from any named sibling, so it lands at a strong 4 rather than 5.

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?

Provides real context for when this applies (first request claims the name, key is scoped to one agent_id) and implies the key is required before checks can be submitted. It does not state prerequisites such as authentication or rate limits, and no alternatives are named.

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.