Skip to main content
Glama
Sign In
kanbn-mcp

kanbn-mcp

by kjduling
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kanbn_burndown

Retrieve burndown chart data from a Kanbn board as an object, with options to filter by dates, columns, sprints, and assignees for progress tracking.

Instructions

Get burndown chart data as an object.

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

Input Schema

NameRequiredDescriptionDefault
pathNoPath to the project root directory
datesNoDates defining a range to show a chart for (defaults to no date filter)
columnsNoOnly show tasks in these columns
sprintsNoSprint names or 1-based numbers to show charts for (defaults to the current sprint)
assignedNoOnly show tasks assigned to this user
normaliseNoDate normalisation mode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says data is returned as an object; it does not disclose whether this is a safe read operation, how dates/sprints are normalized, what defaults apply, or whether the tool can fail or mutate anything.

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?

The description is a single front-loaded sentence with no wasted words. It is efficient, though it is so terse that it sacrifices useful context.

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?

With six optional parameters, no output schema, and many sibling tools, the description is incomplete. It does not explain what the returned burndown object contains, how the parameters interact, what defaults exist, or when this tool is the right choice.

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 the parameters are already documented in the schema. The description adds no additional meaning beyond the schema, but the baseline 3 is appropriate because the schema fully covers each parameter's purpose.

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 uses a specific verb ('Get') and a specific resource ('burndown chart data'), and states the return shape ('as an object'). This clearly distinguishes it from sibling tools such as kanbn_status or kanbn_search, none of which mention burndown data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus alternatives, no context about sprints or board state, and no exclusions. An agent must infer usage solely from the tool name and the generic verb 'get'.

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