Skip to main content
Glama

sprint_health

Read-onlyIdempotent

Sprint/delivery health advisor. POST 1-24 sprints (committed/completed points, optional per-ticket estimate-vs-actual data) and get computed metrics each with a good/warn/bad health tag: velocity avg + trend + stability, commitment reliability, spillover rate, mid-sprint scope change, estimate accuracy (median + chronic-overrun pct), and WIP concentration per assignee. Plus an overall grade and a ranked what-to-fix-first focus list. Pure math + advisory, no LLM.

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": {
      "sprints": "<sprints>"
    },
    "name": "sprint_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
sprintsYesOldest first, 1-24 sprints.
team_sizeNoPeople on the team; enables per-person velocity.
sprint_length_daysNoDefault 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • addedInput schema / properties / sprint_length_days / maximum
      Added value: +60
    • addedInput schema / properties / sprint_length_days / minimum
      Added value: +1
    • changedInput schema / properties / sprint_length_days / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / sprints / description
      Previous value: -"Oldest first: [{name, committed_points, completed_points, added_points?, spillover_points?, tickets?: [{key, estimate_hours, actual_hours, status, assignee}]}]."New value: +"Oldest first, 1-24 sprints."
    • addedInput schema / properties / sprints / items / description
      Added value: +"One sprint."
    • addedInput schema / properties / sprints / items / properties
      Added value: +{
      +  "added_points": {
      +    "description": "Points added mid-sprint (scope creep).",
      +    "minimum": 0,
      +    "type": "number"
      +  },
      +  "committed_points": {
      +    "description": "Points committed at sprint start.",
      +    "minimum": 0,
      +    "type": "number"
      +  },
      +  "completed_points": {
      +    "description": "Points completed.",
      +    "minimum": 0,
      +    "type": "number"
      +  },
      +  "name": {
      +    "description": "Sprint name; defaults to sprint-N.",
      +    "type": [
      +      "string",
      +      "number"
      +    ]
      +  },
      +  "spillover_points": {
      +    "description": "Points carried over. Default committed - completed.",
      +    "minimum": 0,
      +    "type": "number"
      +  },
      +  "tickets": {
      +    "description": "Optional, max 500. Enables estimate-accuracy and load checks.",
      +    "items": {
      +      "description": "One ticket.",
      +      "properties": {
      +        "actual_hours": {
      +          "description": "Hours actually spent.",
      +          "type": "number"
      +        },
      +        "assignee": {
      +          "description": "Owner, for the per-person load check.",
      +          "type": "string"
      +        },
      +        "estimate_hours": {
      +          "description": "Estimated hours.",
      +          "type": "number"
      +        },
      +        "key": {
      +          "description": "Ticket key. Informational.",
      +          "type": "string"
      +        },
      +        "status": {
      +          "description": "Ticket status. Informational.",
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "maxItems": 500,
      +    "type": "array"
      +  }
      +}
    • addedInput schema / properties / sprints / items / required
      Added value: +[
      +  "committed_points",
      +  "completed_points"
      +]
    • addedInput schema / properties / sprints / maxItems
      Added value: +24
    • addedInput schema / properties / sprints / minItems
      Added value: +1
    • addedInput schema / properties / team_size / description
      Added value: +"People on the team; enables per-person velocity."
    • addedInput schema / properties / team_size / maximum
      Added value: +100
    • addedInput schema / properties / team_size / minimum
      Added value: +1
    • changedInput schema / properties / team_size / type
      Previous value: -"number"New value: +"integer"
  2. First observed

TDQS

A3.5/5.0
Behavior3/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 genuinely useful behavioral context beyond that: the analysis is 'pure math + advisory, no LLM' (i.e. deterministic and reproducible) and the graded output is advisory only. It stops short of explaining how good/warn/bad thresholds are set or how missing optional data degrades the report.

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?

Purpose and input shape are front-loaded in the first sentence, and the second sentence adds the non-obvious 'no LLM' guarantee. It is dense and list-heavy but nearly every clause carries information; the metric enumeration is long yet earns its place by telling the agent what comes back.

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?

There is no output schema, so the description must describe returns, and it does so adequately at the shape level (per-metric tags, overall grade, ranked fix list). For a three-parameter, input-heavy analyzer the coverage is solid, with the only real gaps being how thresholds are decided and how partial data affects which metrics are produced.

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 parameter and nested field is already documented in the schema, which sets the baseline at 3. The description adds only light reinforcement by naming the optional per-ticket estimate-vs-actual data as the enabler of estimate accuracy and per-assignee load, but it never mentions team_size or sprint_length_days and adds no format or syntax 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 description states a specific verb+resource ('Sprint/delivery health advisor ... POST 1-24 sprints ... get computed metrics') and enumerates exactly which metrics are returned (velocity trend/stability, commitment reliability, spillover, scope change, estimate accuracy, WIP concentration) plus the overall grade and ranked focus list. It does not, however, differentiate itself from adjacent siblings like estimate_sanity, commit_hygiene, or worklog_guardrail, so an agent may hesitate between them.

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: send 1-24 sprints oldest-first and receive a health report, with per-ticket data optional to unlock extra checks. There is no explicit when-to-use vs when-not guidance and no named alternative for narrower questions (e.g. single-estimate sanity), leaving routing decisions to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.