Skip to main content
Glama
Sign In
mcp-task-tools

mcp-task-tools

by rog0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

burndown_calculator

Calculate sprint burndown chart data by providing tasks with story points and sprint duration. Get ideal vs actual burndown, velocity metrics, and completion forecast.

Instructions

Calculate sprint burndown chart data. Given tasks with story points and sprint duration, computes ideal vs actual burndown, velocity metrics, and completion forecast.

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": {
      "tasks": "<tasks>",
      "sprint_duration_days": "<sprint_duration_days>",
      "current_day": "<current_day>"
    },
    "name": "burndown_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
sprint_nameNoName of the sprint
tasksYesSprint tasks with points and completion data
sprint_duration_daysYesTotal sprint duration in days
current_dayYesCurrent day of the sprint (0-indexed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Without annotations, the description carries the burden. It discloses that the tool computes ideal vs actual burndown, velocity, and forecast, suggesting read-only calculation. However, it does not confirm side effects (e.g., if it stores data) or mention permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose, no redundant words. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description does not describe the return format or structure of the burndown data, velocity, or forecast. This leaves ambiguity for a complex calculation output.

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?

All parameters have descriptions in the schema (100% coverage), so the baseline is 3. The description adds context that parameters relate to burndown calculation but does not enhance syntax or format details beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Calculate sprint burndown chart data' with specific outputs (ideal vs actual burndown, velocity metrics, completion forecast). It distinguishes from sibling tools like priority_sorter and standup_generator.

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 description implies usage context (tasks with story points and sprint duration) but does not explicitly state when to use this tool vs alternatives like time_estimator or todo_manager. No when-not or exclusion guidance.

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

Deploy Server

Other Tools