Skip to main content
Glama

jira_create_sprint

Create a new sprint on a Scrum board to plan upcoming work; new sprints start in future state, accept ISO dates and a goal, and can receive issues afterward.

Instructions

Create a new sprint on a Scrum board for planning upcoming work. New sprints start in "future" state. Use jira_move_issues_to_sprint to add issues after creation. Dates should be in ISO format.

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": {
      "name": "<name>",
      "boardId": "<boardId>"
    },
    "name": "jira_create_sprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNoSprint goal - what the team aims to achieve
nameYesSprint name (e.g., "Sprint 5", "January Sprint")
boardIdYesScrum board ID where sprint will be created (get from jira_get_boards)
endDateNoSprint end date (ISO format: 2024-01-29T17:00:00.000Z)
startDateNoSprint start date (ISO format: 2024-01-15T09:00:00.000Z)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose a genuinely useful trait: new sprints are created in "future" state, so no work is active immediately. It also flags the Scrum-board requirement. It omits permissions/auth needs, name-uniqueness or conflict behavior, and what is returned on success, leaving meaningful gaps for a mutation tool.

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?

Three short sentences, front-loaded with the core action, and each carries content except the closing ISO-format reminder, which duplicates the schema. Nearly zero waste overall.

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 five-parameter create tool with no output schema and no annotations, the description covers purpose, resulting state, the Scrum-board constraint, and the natural next step. Missing permission and error/conflict behavior keeps it from being fully complete.

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%, with each of the five fields already documented including ISO date examples and the pointer to jira_get_boards for boardId. The description's only added parameter note, "Dates should be in ISO format," merely restates the schema, so the baseline of 3 applies.

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 first sentence states a specific verb and resource ("Create a new sprint on a Scrum board") plus the intent (planning upcoming work), which is enough to distinguish it from jira_update_sprint and jira_get_sprints. It stops short of explicitly contrasting with those siblings, so it lands just under the top mark.

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?

It gives clear workflow context by routing the agent to jira_move_issues_to_sprint for populating the sprint after creation, and it implies the board must be Scrum-type. It does not state when to use this instead of jira_update_sprint (e.g. for editing an existing sprint) or any preconditions like permissions.

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