Skip to main content
Glama

calibrate_judge

Measure LLM judge agreement with human labels using Cohen's kappa with bootstrap CI, plus majority baseline and inter-human ceiling to contextualize accuracy and detect chance-level performance.

Instructions

Measure whether an LLM judge agrees with human labels beyond chance.

Reports Cohen's κ (weighted, for ordinal scores) with a bootstrap CI, next to the two numbers that make it legible: the majority-class baseline, and the inter-human ceiling. Accuracy alone is the trap — on a set that's 78% pass, a judge that always says "pass" scores 78%.

Args: judge_path: JSONL/CSV of judge outputs. Needs an id and a score/label/choice. gold_path: JSONL/CSV of human labels, joined on the same id. weights: "auto" | "linear" | "quadratic" | "none". Auto uses weighted κ for ordinal scales with >2 levels, which is nearly always what you want — plain κ treats 9-vs-8 as exactly as wrong as 9-vs-1. human_ceiling: inter-human κ, if you measured it. Without this we cannot tell a bad judge from an underdefined task. Also read from a rater_agreement field in the gold file. verbose: include evidence, fixes and citations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
verboseNo
weightsNoauto
gold_pathYes
judge_pathYes
human_ceilingNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations exist, so the description carries full burden. It transparently describes outputs (kappa, bootstrap CI, baseline, ceiling) and warns about the accuracy trap. However, it does not explicitly disclose read-only or safety properties, though the statistical nature implies no side effects.

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?

The description is front-loaded with a clear introduction and then structured parameter documentation. While slightly verbose, every sentence adds value, and the format is easy to parse.

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?

Given that an output schema exists (not shown but noted), the description adequately covers the tool's purpose, parameters, and key behavioral notes. No gaps remain for a calibration tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description includes a detailed Args section that explains each parameter's purpose, default behavior (e.g., auto weights), and optional nature. This adds meaning far beyond the input schema alone.

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 clearly states the tool measures agreement between an LLM judge and human labels beyond chance, using Cohen's weighted kappa. This specific verb+resource distinguishes it from siblings like audit_judge or bias_probe.

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?

The description implicitly conveys usage (when you have judge outputs and human gold labels), but does not explicitly state when to use this tool versus alternatives like audit_judge or detect_judge_drift. No when-not-to-use guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/asif786ka/judge-audit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server