Skip to main content
Glama
kunwarVivek

mcp-github-project-manager

get_iteration_by_date

Identify which GitHub project iteration contains a specific date by providing the project ID and target date. This tool helps with sprint planning and timeline management in GitHub Projects V2.

Instructions

Find which iteration contains a specific date

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYes
dateYes
fieldNameNo

Implementation Reference

  • The main handler function that implements the get_iteration_by_date tool logic. It retrieves the iteration configuration for the project and finds which iteration contains the specified date by comparing date ranges.
    async getIterationByDate(data: {
      projectId: string;
      date: string;
      fieldName?: string;
    }): Promise<{
      id: string;
      title: string;
      startDate: string;
      endDate: string;
      duration: number;
    } | null> {
      try {
        const config = await this.getIterationConfiguration(data);
        const targetDate = new Date(data.date);
    
        for (const iteration of config.iterations) {
          const start = new Date(iteration.startDate);
          const end = new Date(start);
          end.setDate(end.getDate() + iteration.duration);
    
          if (targetDate >= start && targetDate < end) {
            return {
              id: iteration.id,
              title: iteration.title,
              startDate: iteration.startDate,
              endDate: end.toISOString(),
              duration: iteration.duration
            };
          }
        }
    
        return null;
      } catch (error) {
        throw this.mapErrorToMCPError(error);
      }
    }
  • ToolDefinition object including the Zod input schema, description, and examples for the get_iteration_by_date tool.
    export const getIterationByDateTool: ToolDefinition<GetIterationByDateArgs> = {
      name: "get_iteration_by_date",
      description: "Find which iteration contains a specific date",
      schema: getIterationByDateSchema as unknown as ToolSchema<GetIterationByDateArgs>,
      examples: [
        {
          name: "Find iteration",
          description: "Find which iteration contains a specific date",
          args: {
            projectId: "PVT_kwDOLhQ7gc4AOEbH",
            date: "2025-01-15T00:00:00Z"
          }
        }
      ]
    };
  • Registers the getIterationByDateTool in the central ToolRegistry singleton.
    this.registerTool(getIterationConfigurationTool);
    this.registerTool(getCurrentIterationTool);
    this.registerTool(getIterationItemsTool);
    this.registerTool(getIterationByDateTool);
    this.registerTool(assignItemsToIterationTool);
  • Dispatches tool calls to the ProjectManagementService handler in the main MCP server switch statement.
    case "get_iteration_by_date":
      return await this.service.getIterationByDate(args);
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 of behavioral disclosure. It states the tool finds iterations by date but doesn't explain what 'iteration' means in this context, whether it's read-only or has side effects, error handling, or return format. This is a significant gap for a tool with no annotation coverage.

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 that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse 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 tool's complexity (3 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what an 'iteration' is, how parameters interact, or what the output looks like, leaving the agent with insufficient context to use the tool effectively.

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%, meaning none of the three parameters (projectId, date, fieldName) are documented in the schema. The description mentions 'date' but doesn't explain its format or purpose, and it omits 'projectId' and 'fieldName' entirely. It adds minimal value beyond the schema, failing to compensate for the coverage gap.

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 'Find which iteration contains a specific date' clearly states the tool's purpose with a specific verb ('Find') and resource ('iteration'), and it distinguishes the tool by focusing on date-based iteration lookup. However, it doesn't explicitly differentiate from sibling tools like 'get_current_iteration' or 'get_iteration_items', which might have overlapping functionality.

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. It doesn't mention prerequisites, context (e.g., project management scenarios), or comparisons to sibling tools like 'get_current_iteration' or 'get_iteration_configuration', leaving the agent to infer usage from the tool 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