Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

List sprints

jira_list_sprints
Read-only

List sprints for a Jira Scrum board, optionally filtered by active, future, or closed state, to inspect board planning data.

Instructions

List sprints of a Scrum 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": "jira_list_sprints"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNo
boardIdYes
instanceNoJira instance name (see jira_list_instances). Optional: calls are routed automatically by 'name:KEY' prefixes, issue URLs, project-key mapping, the default instance, or when only one instance exists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description's one added behavioral fact is that the board must be a Scrum board (sprints don't exist on Kanban boards), but it doesn't say what happens otherwise or what the default state filter is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero wasted words, but it is terse to the point of under-specification rather than genuinely concise. Structure is fine; content density is too low.

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 three-parameter tool with no output schema and no annotation coverage of return shape, the description leaves key questions open: whether boardId must be a Scrum board, what state defaults to, and what fields a sprint contains. Only the safety profile is covered, and that comes from annotations.

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?

Schema coverage is only 33%: boardId has no description at all and state has an enum but no explanation of default behavior. The phrase "of a Scrum board" hints that boardId must reference a Scrum-type board, but the description does not compensate for the undocumented parameters.

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?

States a specific verb and resource ("List sprints") and scopes it to "a Scrum board", which distinguishes it from jira_list_boards and other list tools. It does not explicitly name or contrast with any sibling, but the resource is unambiguous.

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 on when to call this versus jira_list_boards or other list tools, and no mention of how the optional state filter should be used. The agent must infer everything from the required boardId.

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