Skip to main content
Glama

create_sprint

Create a new development sprint in GitHub projects by defining title, description, dates, and linking issues for structured project planning.

Instructions

Create a new development sprint

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
descriptionYes
startDateYes
endDateYes
issueIdsYes

Implementation Reference

  • Core handler function that executes the create_sprint tool logic. Validates input, constructs Sprint data object, and delegates creation to GitHubSprintRepository.
    async createSprint(data: {
      title: string;
      description: string;
      startDate: string;
      endDate: string;
      issueIds?: string[];
    }): Promise<Sprint> {
      try {
        // Create data object that matches the expected type
        const sprintData: Omit<Sprint, "id" | "createdAt" | "updatedAt"> = {
          title: data.title,
          description: data.description,
          startDate: data.startDate,
          endDate: data.endDate,
          status: ResourceStatus.PLANNED,
          issues: data.issueIds?.map(id => id.toString()) || []
        };
    
        return await this.sprintRepo.create(sprintData);
      } catch (error) {
        throw this.mapErrorToMCPError(error);
      }
    }
  • Zod schema defining input validation for create_sprint tool arguments, including title, description, dates, and optional issue IDs.
    // Schema for create_sprint tool
    export const createSprintSchema = z.object({
      title: z.string().min(1, "Sprint title is required"),
      description: z.string().min(1, "Sprint description is required"),
      startDate: z.string().datetime("Start date must be a valid ISO date string"),
      endDate: z.string().datetime("End date must be a valid ISO date string"),
      issueIds: z.array(z.string()).default([]),
    });
    
    export type CreateSprintArgs = z.infer<typeof createSprintSchema>;
  • Registers the createSprintTool in the central ToolRegistry during initialization.
    this.registerTool(createSprintTool);
  • MCP server dispatch handler that routes create_sprint tool calls to ProjectManagementService.createSprint.
    case "create_sprint":
      return await this.service.createSprint(args);
  • ToolDefinition object for create_sprint, including name, description, schema reference, and usage examples.
    export const createSprintTool: ToolDefinition<CreateSprintArgs> = {
      name: "create_sprint",
      description: "Create a new development sprint",
      schema: createSprintSchema as unknown as ToolSchema<CreateSprintArgs>,
      examples: [
        {
          name: "Create two-week sprint",
          description: "Create a two-week sprint with initial issues",
          args: {
            title: "Sprint 1: User Authentication",
            description: "First sprint focused on user authentication features",
            startDate: "2025-06-01T00:00:00Z",
            endDate: "2025-06-15T00:00:00Z",
            issueIds: ["101", "102", "103"]
          }
        }
      ]
    };
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'create' implies a write operation, but doesn't disclose behavioral traits like required permissions, whether it's idempotent, what happens on conflicts, or error handling. This leaves significant gaps for a mutation tool.

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, efficient sentence with no wasted words. It's front-loaded and appropriately sized for the tool's purpose, making it easy to scan and understand quickly.

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 of a 5-parameter mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavior, parameter usage, and return values, making it insufficient for an AI agent to use the tool effectively without additional context.

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 description coverage is 0%, so the description must compensate but adds no parameter information. It doesn't explain what 'issueIds' should contain, date formats for 'startDate' and 'endDate', or constraints on 'title' and 'description'. With 5 undocumented parameters, this is inadequate.

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?

The description clearly states the verb ('create') and resource ('development sprint'), making the purpose evident. However, it doesn't differentiate from sibling tools like 'create_milestone' or 'create_project', which also create development artifacts, so it's not fully specific to sibling context.

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 like 'plan_sprint' or 'create_milestone'. The description lacks context about prerequisites, such as needing an existing project or milestone, or exclusions for overlapping functionality with siblings.

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/HarshKumarSharma/MCP'

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