Skip to main content
Glama

sprint_forecast

Read-onlyIdempotent

Forecast sprint completion dates from backlog size and historical velocity, returning required sprint count and a pessimistic estimate based on velocity variance.

Instructions

Forecast sprint completion date from backlog size and historical velocity.

Computes average velocity from sprint history, converts story points to hours, and returns required sprints with pessimistic estimate based on velocity variance. Use when planning a sprint completion date from backlog size and velocity history.

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": {
      "backlog_points": "<backlog_points>",
      "velocity_history": "<velocity_history>"
    },
    "name": "sprint_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNoOptional project/repo identifier this estimate belongs to, for cross-project analytics.
ai_nativeNoDegree of AI assistance: 0.0 = fully human, 1.0 = fully AI-native, 0.5 = hybrid. Accepts boolean for backward compatibility (true=1.0, false=0.0).
task_typeNoOptional task type for feedback matching.
session_idNoOptional session identifier (minted by a calling agent/hook) used to deduplicate repeated estimate calls for the same task within a session.
task_labelNoOptional free-text label identifying the task this estimate is for (e.g. an issue key or short title). Surfaced on get_pending_estimates output for triage.
backlog_pointsYesTotal story points or effort units remaining in the backlog.
hours_per_sprintNoTotal productive engineering hours available per sprint (accounts for meetings, overhead).
velocity_historyYesHistorical velocities from completed sprints. Minimum 1 data point; 3+ recommended for meaningful forecasts.
sprint_length_daysNoCalendar days in a single sprint cycle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.8.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / ai_native / default
      Removed value: -1
    • addedInput schema / properties / project
      Added value: +{
      +  "description": "Optional project/repo identifier this estimate belongs to, for cross-project analytics.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / session_id
      Added value: +{
      +  "description": "Optional session identifier (minted by a calling agent/hook) used to deduplicate repeated estimate calls for the same task within a session.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / task_label
      Added value: +{
      +  "description": "Optional free-text label identifying the task this estimate is for (e.g. an issue key or short title). Surfaced on get_pending_estimates output for triage.",
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A3.7/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 safety needs no prose. The description still adds value beyond them by disclosing the computation path (average velocity → point-to-hour conversion → required sprints) and the fact that a pessimistic estimate derived from velocity variance is included.

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?

Two sentences, front-loaded with the core action and computational method, which is good structure. The second sentence largely repeats the first ('completion date from backlog size and velocity history'), so there is a small amount of waste.

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 what comes back (required sprints plus a variance-based pessimistic estimate), which an agent needs for planning. Remaining gaps—units of the pessimistic bound and how variance is applied—are minor for a deterministic read-only calculator whose parameters are fully documented.

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%, so every one of the nine parameters is already documented in the schema, which sets the baseline at 3. The description only loosely connects to parameters by mentioning backlog size, velocity history, and story-point-to-hours conversion; it adds no format or constraint detail beyond the schema.

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 first sentence names a specific verb and resource: 'Forecast sprint completion date from backlog size and historical velocity.' That is enough to tell it apart from siblings like pert_estimate or monte_carlo_schedule, which imply different methods, though the description never names an alternative explicitly.

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 second sentence ('Use when planning a sprint completion date from backlog size and velocity history') is essentially a restatement of the purpose rather than real routing guidance. It gives no when-not-to-use conditions and does not mention when monte_carlo_schedule, pert_estimate, or reference_class_estimate would be preferable.

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