Skip to main content
Glama
ParasSolanki

Jira MCP Server

by ParasSolanki

list_sprints_from_board

Retrieve all sprints from a specified Jira board. Filter results by start index and maximum count.

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 main handler function for the list_sprints_from_board tool. Takes boardId, optional startAt and maxResults, constructs a Jira REST API URL, fetches sprints from the board via the $jiraJson helper, and returns the JSON result.
    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 input schema defining the expected parameters: boardId (string, required), maxResults (number, optional, max 100), startAt (number, optional).
    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"),
    });
  • Tool definition object (LIST_SPRINTS_FROM_BOARD_TOOL) with name 'list_sprints_from_board', description, and inputSchema converted from Zod schema to JSON Schema format.
    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)
    Registration of LIST_SPRINTS_FROM_BOARD_TOOL in the tools array that is returned when the server handles ListToolsRequestSchema.
    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[];
  • CallToolRequestSchema handler that routes the 'list_sprints_from_board' tool name, validates input via safeParse, calls listSprintsFromBoard, handles errors, and returns the JSON response.
    if (name === LIST_SPRINTS_FROM_BOARD_TOOL.name) {
      const input = listSprintsFromBoardInputSchema.safeParse(args);
    
      if (!input.success) {
        return {
          isError: true,
          content: [{ type: "text", text: "Invalid input" }],
        };
      }
    
      const result = await listSprintsFromBoard(input.data);
    
      if (result.isErr()) {
        console.error(result.error.message);
        return {
          isError: true,
          content: [{ type: "text", text: "An error occurred" }],
        };
      }
    
      return {
        content: [
          { type: "text", text: JSON.stringify(result.value, null, 2) },
        ],
      };
    }
Behavior2/5

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

No annotations provided, and description does not disclose behaviors like pagination (maxResults, startAt), ordering, or scope (active/future/closed sprints). Full burden on description, which fails.

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?

Single sentence with no wasted words. Perfectly concise.

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?

Does not mention return format, pagination behavior, or constraints like max sprints. Incomplete for a 3-parameter tool with no output schema.

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 baseline is 3. Description does not add any additional meaning beyond schema parameter names.

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?

Clearly states verb 'list', resource 'sprints', and scope 'from a board'. Distinguishes from sibling tools like list_boards and list_issues_from_sprint.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use or alternatives, but purpose is straightforward given sibling names. Lacks exclusions or prerequisites.

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