Skip to main content
Glama

feedback_health

Read-onlyIdempotent

Assess estimation feedback-loop health with total estimates, actuals, match rate, MAPE by tool and task type, and auto-calibration readiness.

Instructions

Get a health report on the estimation feedback loop.

Shows total estimates, actuals, match rate, MAPE by tool and task type, and self-improvement readiness (which types have enough data for auto-calibration). Use when checking whether you have enough recorded actuals for calibration to kick in.

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": "feedback_health"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds behavior beyond that by disclosing the metrics returned and the notion of a readiness threshold (which task types have enough data for auto-calibration) — useful because no output schema exists.

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?

Three short sentences, front-loaded with the core action, then the payload, then the usage trigger. The last sentence lightly restates the 'self-improvement readiness' idea already implied by the second, a minor redundancy but not bloat.

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 carries the burden of describing the return payload, and it does so by naming the key metrics and the readiness signal. It stops short of covering degenerate states (e.g., what the report shows when there are no actuals at all), but is otherwise sufficient for calling a zero-parameter diagnostic.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the description correctly implies no inputs are required. Baseline 4 applies, with no schema-level meaning left unaddressed.

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?

States a specific verb and resource ('Get a health report on the estimation feedback loop') and enumerates the report contents: totals, actuals, match rate, MAPE by tool and task type, and self-improvement readiness. This is clearly differentiated from accuracy_trend and calibrate_estimates by framing it as a readiness/diagnostic check, though it never names those alternatives 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?

'Use when checking whether you have enough recorded actuals for calibration to kick in' gives a concrete triggering condition and implicitly distinguishes this from the calibration action itself. There is no explicit when-not guidance, but the framing is specific enough to route an agent.

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