Skip to main content
Glama

accuracy_trend

Read-onlyIdempotent

Track estimation accuracy over time with sliding-window MAPE, compare results to a 25% industry baseline, and see whether estimates are improving, degrading, or stable.

Instructions

Track estimation accuracy improvement over time.

Computes sliding-window MAPE and compares against industry baseline (25%). Shows whether your estimates are improving, degrading, or stable. Industry research shows estimation accuracy does NOT improve with experience (Cao 2022) — self-correcting systems like Epoch can buck this trend.

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

Input Schema

NameRequiredDescriptionDefault
team_idNoOptional team identifier to scope historical data.
window_sizeNoNumber of records per sliding window.

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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds real behavioral context beyond that: the sliding-window computation, the 25% baseline reference point, and the three-way trend classification. It does not disclose data requirements (sufficient historical records) or how sparse data is handled, and the closing research/Epoch sentence is persuasive framing rather than operational detail.

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?

The first three sentences are front-loaded and earn their place by defining the computation, baseline, and output classification. The final sentence about Cao 2022 and Epoch bucking the trend is motivational framing with no actionable content for invoking the tool, and it dilutes an otherwise tight definition.

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?

For a read-only analytics tool with two fully documented optional parameters and no output schema, the description conveys what the result means (trend direction plus MAPE against a baseline). Missing pieces are minor: no statement that historical records with actuals are required, and no routing to sibling tools for related analyses.

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% across both parameters, including team_id scoping and window_size with its default of 50 and minimum of 5, so the schema already carries the semantics. The description mentions the sliding window conceptually but adds no guidance on window_size choice or what team_id scoping changes in the result. Baseline 3 is appropriate.

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: it computes sliding-window MAPE and compares it against a 25% industry baseline to classify accuracy as improving, degrading, or stable. That is concrete enough to distinguish it from analytical siblings like compare_models or calibrate_estimates. It stops short of naming those siblings directly, so the differentiation is inferential rather than explicit.

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?

Usage is implied by 'Track estimation accuracy improvement over time', which suggests calling it when you want a longitudinal accuracy read. There is no explicit when-not guidance, no prerequisites such as needing recorded actuals, and no named alternative for related needs like calibration or model comparison. The agent must infer placement among the many estimation siblings.

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