idea-base-mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

create_sprint

Opens a sprint on a product, defaulting to the next cadence period when dates are omitted and rejecting duplicates for the same period.

Instructions

Open a sprint on a product. With no dates it opens the NEXT one on the product's cadence, which is the normal case; pass starts_on/ends_on only to set an explicit window. One sprint per product per period — a second for the same period is refused rather than duplicated.

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": {
      "product_id": "<product_id>"
    },
    "name": "create_sprint"
  }
}

Input Schema

Name	Required	Description
`goal`	No	What this sprint is meant to achieve
`name`	No	Optional. Defaults to its date range.
`state`	No	Default planned. A sprint cannot be created closed.
`ends_on`	No	YYYY-MM-DD. Omit to run one cadence length from starts_on.
`starts_on`	No	YYYY-MM-DD. Omit to follow the cadence.
`product_id`	Yes	The product to open the sprint on

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.7.0Nov 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the important default cadence behavior and the duplicate-refusal rule for one sprint per product per period, but it does not mention permissions, side effects, or what a successful creation returns.

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, front-loaded with the core action, followed by the normal usage pattern and the duplicate-refusal constraint. There is no wasted wording.

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?

For a six-parameter creation tool with no annotations and no output schema, the description covers creation semantics, date behavior, and the uniqueness constraint. It leaves permission expectations and response details unstated, which is a minor completeness gap.

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 description coverage is 100%, so the schema already documents all six parameters. The description adds useful semantics beyond the schema by explaining the normal omitted-date path and that starts_on/ends_on are only for setting an explicit window, plus the period-uniqueness constraint.

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 the specific verb 'Open a sprint' and resource 'on a product', and immediately clarifies the default cadence-based behavior. It is clearly distinguishable from siblings like close_sprint and list_sprints by the creation action.

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?

Tells the caller that the normal case is to omit dates and let cadence determine the next sprint, and that starts_on/ends_on are only for an explicit window. It does not explicitly name related siblings such as get_sprint_cadence or set_sprint_cadence as alternatives.

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