jira-mcp-server

get_sprints

Retrieve sprints for a Jira board using its ID, with optional state filtering for active, future, or closed sprints.

Instructions

List sprints for a specific board

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": "get_sprints"
  }
}

Input Schema

Name	Required	Description	Default
`state`	No	Filter by state (active, future, closed)
`boardId`	Yes	The ID of the board

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 8, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, and the description only states 'List sprints', omitting any details about pagination, ordering, default state behavior, or errors. It does not disclose the return format.

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?

The description is a single, front-loaded sentence with no filler words, earning 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?

Given the lack of annotations and output schema, the description is incomplete: it doesn't explain what the tool returns, how state filtering works, or any edge cases. The agent would need to infer too much.

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?

The input schema provides complete descriptions for both parameters (boardId and state), so the description adds nothing beyond the schema. Baseline of 3 is appropriate.

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 uses a specific verb 'List' and resource 'sprints' with a scope 'for a specific board', clearly distinguishing it from sibling tools like create_sprint, update_sprint, and delete_sprints.

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?

Provides no guidance on when to use this tool versus alternatives, or any exclusions. It does not mention that boardId is required or how to obtain it, despite get_boards being a sibling.

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