Skip to main content
Glama

calibrate_estimates

Read-onlyIdempotent

Recalculate team-specific correction factors by comparing estimated versus actual hours, then return recommendations to improve estimation accuracy from historical data.

Instructions

Recalculate team-specific correction factors from historical estimation data.

Compares estimated vs actual hours to compute a correction multiplier. Requires PM system integration for best results. Returns recommendations for improving estimation accuracy. Use when you have accumulated actuals and want to refresh team calibration factors.

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": {
      "team_id": "<team_id>"
    },
    "name": "calibrate_estimates"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYesTeam identifier whose historical accuracy data should be analysed.
period_daysNoLookback window in calendar days for calibration data.
minimum_samplesNoMinimum number of completed tasks required before producing a calibration factor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: the computation method (estimated vs actual hours), the dependency that PM system integration is required 'for best results', and that the output is recommendations rather than applied changes, which resolves how a 'recalculate' verb squares with a read-only tool.

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 opening sentence front-loads the core action and is followed by progressively finer detail. Five short sentences carry no filler, though the 'Returns recommendations for improving estimation accuracy' line is close to redundant with the 'refresh calibration factors' framing.

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?

With no output schema, the description usefully states the return concept (recommendations plus a correction multiplier) and flags the PM integration prerequisite. For a three-parameter analytical tool with full schema coverage, nothing essential to calling it correctly appears to be missing.

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

Parameters3/5

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

Schema description coverage is 100% and all three parameters (team_id, period_days, minimum_samples) are documented in the schema itself. The description only loosely gestures at 'historical estimation data' and 'accumulated actuals' without adding semantics for the lookback window or sample threshold, so the baseline 3 applies.

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 states a specific verb and resource: 'Recalculate team-specific correction factors from historical estimation data', and explains the computation is a comparison of estimated vs actual hours. This clearly separates it from reporting-style siblings such as accuracy_trend or get_pending_estimates, though no sibling is named explicitly.

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?

It gives a concrete trigger: 'Use when you have accumulated actuals and want to refresh team calibration factors', which is exactly the condition that selects this tool. It stops short of naming an alternative or stating when not to use it, so it lands just below the top band.

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