Skip to main content
Glama

Task burndown

burndown
Read-only

Burndown and flow metrics for the vault's tasks, computed from their recorded history. scope is a concept id (an iteration, milestone, feature, domain or any concept tasks are part_of / realize, including nested containers) or tag:<tag>; omit it for every task. Returns, for the window: open vs done over time with an ideal line when the scope has start/end dates, scope changes, velocity per iteration or week, a projected completion date with an optimistic/pessimistic range, lead and cycle time per agent label, and claims held longer than staleAfterHours. metrics limits the sections returned. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
toNoWindow end (YYYY-MM-DD or ISO). Default: the later of the scope's endDate and now.
fromNoWindow start (YYYY-MM-DD or ISO). Default: the scope's startDate, else 8 weeks ago.
unitNoCount tasks (default) or sum their `estimate` points.
scopeNoA concept id (iteration, milestone, feature, domain, …) or `tag:<tag>`. Omit for every task in the vault.
bucketNoSeries granularity. Default: day for windows up to 120 days, else week.
metricsNoSections to include: series, scopeChanges, velocity, projection, cycle, agents, stale (default all).
staleAfterHoursNoA claim held longer than this is stale (default 24).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds real context: metrics are derived from recorded history, defaults for the window, projection ranges, and stale-claim detection. It does not discuss cost or performance of computing over the whole vault, but the behavioral picture is solid.

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?

Front-loads the purpose, then packs scope, return sections, and the metrics filter into dense but purposeful sentences. Slightly long clauses, but no filler.

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

Completeness5/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 returns and does so by enumerating every section (series, scope changes, velocity, projection, cycle time, agents, stale claims). An agent knows what it will get and how to narrow it.

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?

Schema coverage is 100%, so the baseline is 3; the description still adds meaning by clarifying that `scope` accepts nested containers and `tag:<tag>` and that omitting it means every task, plus what `metrics` sections control.

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?

States a specific verb+resource ('Burndown and flow metrics for the vault's tasks') and the data source ('computed from their recorded history'), which clearly separates it from siblings like list_tasks or vault_stats.

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?

Explains how to scope the query (concept id, tag:<tag>, or omit for all tasks) and how to limit output via `metrics`, giving clear usage context. It stops short of naming an alternative tool or an explicit when-not-to-use condition.

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.

Resources