Skip to main content
Glama
Sign In
taiga-mcp

taiga-mcp

by kiet0807
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Read one sprint

get_sprint
Read-only

Retrieve a Taiga sprint's full details—dates, completed stories, tasks, points, and daily burndown to today—to check progress, assess if work is on track, or prepare a sprint review.

Instructions

Read one sprint of a Taiga project in full: dates, how many stories, tasks and points are done, and the burndown day by day (points still open against the ideal line), up to today. Use it for "how is the sprint going", "are we on track", or a sprint review. For the stories or tasks in it use list_user_stories or list_tasks with sprint.

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": {
      "project": "<project>"
    },
    "name": "get_sprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
sprintNoA sprint name from list_sprints, or "current" for the sprint running today (the default).current
projectYesProject slug as given by list_projects, e.g. "acme-billing". Not the display name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

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 openWorldHint=true, so safety is covered, and the description adds the meaningful extra behavior: burndown is computed only 'up to today' rather than the full sprint. It doesn't touch on authentication or result size, but for a read-only reporting tool that omission is minor.

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?

Three sentences, zero filler: the main capability is front-loaded, usage triggers follow, and the sibling routing hint closes. Every sentence carries distinct information.

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 does the work of describing the return shape (aggregate counts plus burndown against an ideal line), which is what an agent needs to interpret results. It stops short of describing pagination or result volume, but for a single-entity read that is a minor gap.

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 coverage is 100%, so both parameters, including the `current` default and the slug-vs-name distinction, are already documented in the schema. The description only adds the side note that `sprint` can be reused as a filter on list_user_stories/list_tasks, which is useful but marginal.

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?

Names a specific verb and resource ('Read one sprint of a Taiga project') and enumerates the payload it returns: dates, story/task/point completion, and day-by-day burndown. It also explicitly separates itself from list_user_stories and list_tasks, so an agent can route correctly without inspecting sibling schemas.

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

Usage Guidelines5/5

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

Gives concrete triggers ('how is the sprint going', 'are we on track', a sprint review) and names the alternative tools to use when the caller actually wants the underlying stories or tasks, including the `sprint` filter to pass. The when-to-use and when-to-use-something-else conditions are both stated.

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