Skip to main content
Glama
kunwarVivek

mcp-github-project-manager

get_current_sprint

Retrieve the active sprint from GitHub Projects to track current progress and manage workflow tasks efficiently.

Instructions

Get the currently active sprint

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeIssuesYes

Implementation Reference

  • Implements the core logic to find and return the currently active sprint, optionally including associated issues by calling the sprint repository.
    async getCurrentSprint(includeIssues: boolean = true): Promise<Sprint | null> {
      try {
        const currentSprint = await this.sprintRepo.findCurrent();
    
        if (!currentSprint) {
          return null;
        }
    
        if (includeIssues) {
          // Add issues data to sprint
          const issues = await this.sprintRepo.getIssues(currentSprint.id);
    
          // We can't modify the sprint directly, so we create a new object
          return {
            ...currentSprint,
            // We're adding this property outside the type definition for convenience
            // in the response; it won't affect the actual sprint object
            issueDetails: issues
          } as Sprint & { issueDetails?: Issue[] };
        }
    
        return currentSprint;
      } catch (error) {
        throw this.mapErrorToMCPError(error);
      }
    }
  • Defines the tool schema, input validation (includeIssues boolean), description, and usage examples.
    export const getCurrentSprintTool: ToolDefinition<GetCurrentSprintArgs> = {
      name: "get_current_sprint",
      description: "Get the currently active sprint",
      schema: getCurrentSprintSchema as unknown as ToolSchema<GetCurrentSprintArgs>,
      examples: [
        {
          name: "Get current sprint with issues",
          description: "Get details of the current sprint including assigned issues",
          args: {
            includeIssues: true
          }
        }
      ]
    };
  • Registers the getCurrentSprintTool in the central ToolRegistry singleton.
    this.registerTool(getCurrentSprintTool);
  • Main MCP tool dispatch handler that routes 'get_current_sprint' calls to the ProjectManagementService.
    case "get_current_sprint":
      return await this.service.getCurrentSprint(args.includeIssues);
  • Zod schema definition for tool input parameters.
    export const getCurrentSprintSchema = z.object({
      includeIssues: z.boolean().default(true),
    });
    
    export type GetCurrentSprintArgs = z.infer<typeof getCurrentSprintSchema>;
Behavior1/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 but provides none. It doesn't indicate whether this is a read-only operation, what permissions are required, what happens if no sprint is active, or what the return format looks like. For a tool with zero annotation coverage, this is a significant gap.

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 perfectly concise at just 4 words. It's front-loaded with the core purpose and contains no wasted words. Every word earns its place in communicating the essential function.

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 tool has no annotations, no output schema, and 0% schema description coverage for its single parameter, the description is incomplete. It doesn't explain what 'includeIssues' does, what the return format looks like, or behavioral aspects like error conditions. For a tool with this complexity profile, the description should provide more context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, meaning the single parameter 'includeIssues' is completely undocumented in the schema. The description provides no information about this parameter - not what it does, what values it accepts, or how it affects the response. The description fails to compensate for the schema's lack of documentation.

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 ('Get') and resource ('currently active sprint'), making the purpose immediately understandable. It distinguishes from siblings like 'get_sprint_metrics' or 'list_sprints' by focusing on the current/active sprint specifically. However, it doesn't explicitly contrast with 'get_current_iteration' which might be a similar concept.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when-not-to-use scenarios, or comparison with sibling tools like 'get_current_iteration' or 'get_sprint_metrics'. The agent must infer usage from the name alone.

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/kunwarVivek/mcp-github-project-manager'

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