Skip to main content
Glama

Calibration report

calibration_report

Compare decision confidence against human consensus on stored evaluations by rubric to reveal calibration gaps and align automated scoring with reviewer judgment.

Instructions

Compare decision confidence against human consensus on stored evaluations.

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": {
      "rubricId": "<rubricId>"
    },
    "name": "calibration_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNo
bucketsNo
rubricIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: not whether the tool is read-only, whether it requires prior human submissions, what happens when human consensus is absent, or what form the 'report' takes. Only the vague notion of comparing against 'human consensus on stored evaluations' is added.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single, front-loaded sentence with no filler, which is structurally clean. However, the brevity comes at the cost of under-specification rather than true conciseness, since key operational details are simply absent.

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

Completeness2/5

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

For a three-parameter tool with no annotations, no output schema, and zero schema descriptions, one sentence is far from enough. The agent lacks the information needed to know what rubricId scopes, what target and buckets control, or what the report contains.

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

Parameters2/5

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

Schema description coverage is 0% for three parameters, yet the description explains none of them explicitly; 'confidence' only loosely hints at the target threshold, while rubricId (the required scoping parameter) and buckets (bucket count for the report) are left entirely opaque. The description does not compensate for the schema gap.

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?

The description names a specific verb ('compare') and a specific subject ('decision confidence against human consensus on stored evaluations'), so an agent can tell it produces a calibration/comparison report rather than a raw evaluation lookup. It offers no differentiation from overlapping siblings such as compare or check_against_humans, which keeps it below a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (e.g. that human scores must exist), and no pointer to alternative tools for related tasks. The agent must infer the usage context entirely from the tool name and the single sentence.

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