@illodev/taiga-mcp

taiga_milestones_create

Create a new sprint/milestone in Taiga. Specify project, name, start and finish dates to plan and track your iteration schedule.

Instructions

Create a new milestone/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": "<name>",
      "estimated_start": "<estimated_start>",
      "estimated_finish": "<estimated_finish>"
    },
    "name": "taiga_milestones_create"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Sprint name
`slug`	No
`order`	No
`project`	Yes	Project ID
`watchers`	No
`disponibility`	No	Available story points
`estimated_start`	Yes	Start date (YYYY-MM-DD)
`estimated_finish`	Yes	End date (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only says 'create', implying a mutation, but fails to mention required permissions, side effects, or what happens on successful creation. This lack of transparency is a significant gap for a tool that creates persistent data.

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 concise sentence with no wasted words. It is appropriately front-loaded with the core action and resource. However, it is so minimal that it arguably under-specifies the tool's behavior, but for conciseness alone, it earns a high score.

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?

For a tool with 8 parameters, 4 required, no output schema, and no annotations, this description is far too thin. It lacks any context about return values, required fields, error scenarios, or relationships to other entities. The description is insufficient for an agent to invoke the tool with confidence.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool description adds no meaning beyond the input schema. Schema coverage is 63%, leaving parameters like slug, order, watchers, and disponibility undocumented in both schema and description. The description does not clarify any parameter values or relationships, so it fails to compensate for the coverage gap.

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 'Create a new milestone/sprint' clearly states the action (create) and resource (milestone/sprint). It distinguishes from sibling tools like taiga_milestones_update and taiga_milestones_delete by specifying creation, but it doesn't explicitly differentiate from other create tools in the broader context. The verb and resource are specific enough for basic identification.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, such as needing an existing project, or scenarios where another create tool might be more appropriate. The description simply states what it does without any contextual usage direction.

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

Deploy Server