Skip to main content
Glama
ParasSolanki

Jira MCP Server

by ParasSolanki

list_sprints_from_board

Retrieve sprints associated with a specific Jira board to track agile development cycles and project progress.

Instructions

List sprints from a board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesThe ID of the board
maxResultsNoThe maximum number of results to return, (max: 100)
startAtNoThe starting index of the returned boards

Implementation Reference

  • The handler function that implements the core logic of listing sprints from a specified Jira board, handling optional pagination parameters and using the $jiraJson utility to fetch data from the Jira API.
    export async function listSprintsFromBoard(input: ListSprintsFromBoardInput) {
      const url = new URL(
        `/rest/agile/1.0/board/${input.boardId}/sprint`,
        env.JIRA_BASE_URL,
      );
    
      if (input.startAt) url.searchParams.set("startAt", input.startAt.toString());
    
      if (input.maxResults)
        url.searchParams.set("maxResults", input.maxResults.toString());
    
      const json = await $jiraJson(url.toString());
    
      if (json.isErr()) return err(json.error);
    
      return ok(json.value);
    }
  • Zod schema defining the input structure for the tool: required boardId (string) and optional maxResults, startAt (numbers).
    export const listSprintsFromBoardInputSchema = z.object({
      boardId: z.string().describe("The ID of the board"),
      maxResults: z
        .number()
        .optional()
        .describe("The maximum number of results to return, (max: 100)"),
      startAt: z
        .number()
        .optional()
        .describe("The starting index of the returned boards"),
    });
  • Exports the Tool object with name, description, and inputSchema, used for MCP tool registration.
    export const LIST_SPRINTS_FROM_BOARD_TOOL: Tool = {
      name: "list_sprints_from_board",
      description: "List sprints from a board",
      inputSchema: zodToJsonSchema(
        listSprintsFromBoardInputSchema,
      ) as Tool["inputSchema"],
    };
  • src/app.ts:39-48 (registration)
    Registers the list_sprints_from_board tool (via LIST_SPRINTS_FROM_BOARD_TOOL) in the server's list of available tools.
    export const tools = [
      // list
      LIST_PROJECTS_TOOL,
      LIST_BOARDS_TOOL,
      LIST_SPRINTS_FROM_BOARD_TOOL,
      LIST_ISSUES_FROM_SPRINT_TOOL,
    
      // create
      CREATE_ISSUE_TOOL,
    ] satisfies Tool[];
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it lists sprints but doesn't cover key traits like whether it's read-only, requires authentication, includes pagination details (implied by parameters but not described), or error handling. This leaves significant gaps for a tool with parameters and no output schema.

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 a single, efficient sentence ('List sprints from a board') that is front-loaded and wastes no words. However, it's under-specified for a tool with parameters and no output schema, which slightly reduces its effectiveness but not its conciseness.

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 complexity (3 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain return values, error cases, or behavioral context like pagination. For a list operation with parameters, more detail is needed to guide an AI agent effectively.

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%, so the schema already documents all parameters (boardId, maxResults, startAt). The description adds no meaning beyond this—it doesn't explain parameter interactions, default values, or usage examples. Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List sprints from a board' clearly states the action (list) and resource (sprints from a board), but it's vague about scope—it doesn't specify if it lists all sprints, active ones, or something else. It distinguishes from siblings like 'list_boards' or 'list_issues_from_sprint' by focusing on sprints, but lacks specificity to earn a higher score.

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 is provided on when to use this tool versus alternatives. For example, it doesn't mention if it's for retrieving all sprints, filtering by status, or how it relates to siblings like 'list_issues_from_sprint'. The description implies usage for listing sprints but offers no explicit context or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ParasSolanki/jira-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server