Skip to main content
Glama

jira_get_sprints

List sprints for a Scrum board by board ID and filter by active, future, or closed state to review sprint names, goals, dates, and status.

Instructions

List all sprints for a Scrum board. Sprints are time-boxed iterations for completing work. Returns sprint names, goals, dates, and states. Use jira_get_boards first to find the board ID. Filter by state to see only active, future, or closed sprints.

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

Input Schema

NameRequiredDescriptionDefault
stateNoFilter by sprint state: active (current), future (planned), closed (completed)
boardIdYesScrum board ID (get from jira_get_boards with type=scrum)
startAtNoStarting index for pagination
maxResultsNoMaximum number of results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.9/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. It discloses that the tool returns sprint names, goals, dates, and states, which is useful, but it omits pagination behavior, permissions, and the fact that results are capped by maxResults despite saying it lists all sprints.

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 front-loaded with the purpose and return values, then gives prerequisite and filtering guidance. The sentence defining sprints is mildly extraneous but still helpful domain context, and overall the structure is efficient.

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 simple read-only list tool with a fully described schema, the definition covers purpose, return fields, board ID prerequisite, and state filtering. The main missing element is explicit pagination behavior, but the schema exposes the pagination parameters clearly.

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 the input schema already documents boardId, state, startAt, and maxResults. The description reinforces the board ID source and state filtering, but adds little parameter meaning beyond what the schema already provides.

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 states a specific verb and resource: list sprints for a Scrum board. It clearly distinguishes this from creation tools like jira_create_sprint and issue-level tools like jira_get_sprint_issues.

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 a clear prerequisite by telling the agent to use jira_get_boards first to find the board ID, and it explains how to use the state filter. It does not explicitly cover when not to use this tool versus related sprint or issue tools, but the guidance is otherwise clear.

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