Skip to main content
Glama
raalarcon9705

raalarcon-jira-mcp-server

close_sprint

Close an active sprint to mark it complete. The sprint must be active and cannot be reopened.

Instructions

Close and complete a sprint. This action requires the sprint to be in the "active" state. Once closed, the sprint cannot be reopened.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sprintIdYesID of the sprint to close.

Implementation Reference

  • The handler for the close_sprint tool. Validates args using closeSprintSchema, calls jiraClient.closeSprint(), and returns a success message.
    case 'close_sprint': {
      const validatedArgs = await closeSprintSchema.validate(args);
      const _result = await jiraClient.closeSprint(validatedArgs);
    
      return {
        content: [
          {
            type: 'text',
            text: `Sprint ${validatedArgs.sprintId} closed successfully`,
          },
        ],
      };
    }
  • The actual Jira client method that closes a sprint by setting state to 'closed' via partiallyUpdateSprint API.
    async closeSprint(input: CloseSprintInput) {
      try {
        const updateData: PartiallyUpdateSprint = {
          sprintId: input.sprintId,
          state: 'closed'
        };
    
        const response = await this.agileClient.sprint.partiallyUpdateSprint(updateData);
        return response;
      } catch (error) {
        throw new Error(`Failed to close sprint: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
  • Yup schema for close_sprint input validation. Requires 'sprintId' as a number.
    export const closeSprintSchema = yup.object({
      sprintId: yup.number().required('Sprint ID is required'),
    });
  • TypeScript type CloseSprintInput inferred from the yup schema.
    export type CloseSprintInput = yup.InferType<typeof closeSprintSchema>;
  • Tool registration: defines name 'close_sprint', description, and inputSchema (sprintId required number).
    {
      name: 'close_sprint',
      description: 'Close and complete a sprint. This action requires the sprint to be in the "active" state. Once closed, the sprint cannot be reopened.',
      inputSchema: {
        type: 'object',
        properties: {
          sprintId: {
            type: 'number',
            description: 'ID of the sprint to close.',
          },
        },
        required: ['sprintId'],
      },
    },
Behavior3/5

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

The description mentions irreversibility and state requirement, but lacks details on side effects (e.g., impact on issues) and return value. With no annotations, it carries the full burden and leaves gaps.

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?

Two concise sentences, first stating the action and second adding constraints. Every sentence is essential and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool, the description covers prerequisites but omits output/return value and post-close effects. Without output schema, this context would be valuable.

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 already describes the only parameter (sprintId) with 100% coverage. The tool description does not add further parameter meaning beyond the schema, meeting the baseline.

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 clearly states the action ('close and complete a sprint'), the required state (active), and the irreversible nature. It effectively distinguishes from sibling tools like create_sprint or delete_sprint.

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 explicitly requires the sprint to be 'active' and warns about irreversibility. While it doesn't compare to alternatives (e.g., delete_sprint), the context of siblings makes the primary use clear.

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/raalarcon9705/jira-mcp'

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