Skip to main content
Glama
blackgirlbytes

GitHub Calendar MCP Server

get_team_status

Retrieve current development team status including active issues, due items, and recent completions for each member to monitor project progress and workload distribution.

Instructions

Get current status of the development team including active issues, due items, and recent completions for each team member

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that fetches GitHub issues, processes team members' workloads, and returns TeamStatus.
    async getTeamStatus(): Promise<TeamStatus> {
      try {
        // Get all open issues for the team
        const issues = await this.githubClient.getAllTeamIssues();
        
        // Get unique assignees
        const assigneeLogins = this.githubClient.getUniqueAssignees(issues);
        
        // Build team member data
        const members: TeamMember[] = [];
        
        for (const login of assigneeLogins) {
          const memberIssues = issues.filter(issue => 
            issue.assignees.some(assignee => assignee.login === login)
          );
          
          const activeIssues = memberIssues.filter(issue => issue.state === 'open').length;
          const dueToday = this.countDueToday(memberIssues);
          const completedThisWeek = await this.getCompletedThisWeek(login);
          
          // Get avatar from first issue assignee data
          const avatarUrl = memberIssues[0]?.assignees.find(a => a.login === login)?.avatar_url || '';
          
          members.push({
            login,
            avatar_url: avatarUrl,
            activeIssues,
            dueToday,
            completedThisWeek,
            issues: memberIssues
          });
        }
    
        // Sort by workload (most active first)
        members.sort((a, b) => b.activeIssues - a.activeIssues);
    
        const totalActiveIssues = members.reduce((sum, member) => sum + member.activeIssues, 0);
        const totalDueToday = members.reduce((sum, member) => sum + member.dueToday, 0);
    
        return {
          members,
          totalActiveIssues,
          totalDueToday,
          lastUpdated: new Date().toISOString()
        };
      } catch (error) {
        console.error('Error getting team status:', error);
        throw error;
      }
    }
  • src/index.ts:92-100 (registration)
    Registration of the get_team_status tool in the MCP ListToolsRequestHandler, including name, description, and input schema.
    {
      name: 'get_team_status',
      description: 'Get current status of the development team including active issues, due items, and recent completions for each team member',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • TypeScript interface defining the output structure of the get_team_status tool.
    export interface TeamStatus {
      members: TeamMember[];
      totalActiveIssues: number;
      totalDueToday: number;
      lastUpdated: string;
    }
  • MCP CallToolRequestSchema handler case that executes the team status tool and returns formatted response.
    case 'get_team_status': {
      const status = await this.teamStatusTool.getTeamStatus();
      return {
        content: [
          {
            type: 'text',
            text: this.formatTeamStatus(status),
          },
        ],
      };
    }
  • Helper function that formats the raw TeamStatus data into a readable Markdown summary.
    private formatTeamStatus(status: any): string {
      const { members, totalActiveIssues, totalDueToday, lastUpdated } = status;
      
      let output = `## Team Status (as of ${new Date(lastUpdated).toLocaleString()})\n\n`;
      output += `**Overview:** ${totalActiveIssues} active issues, ${totalDueToday} due today\n\n`;
      
      if (members.length === 0) {
        output += 'No team members found with assigned issues.\n';
        return output;
      }
    
      output += '**Team Members:**\n';
      for (const member of members) {
        const { login, activeIssues, dueToday, completedThisWeek } = member;
        output += `- **${login}**: ${activeIssues} active`;
        
        if (dueToday > 0) {
          output += `, ${dueToday} due today`;
        }
        
        if (completedThisWeek > 0) {
          output += `, ${completedThisWeek} completed this week`;
        }
        
        output += '\n';
      }
    
      return output;
    }
Behavior2/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. It describes a read operation ('Get') but doesn't cover critical aspects like permissions required, data freshness, rate limits, or response format. This leaves significant gaps for a tool that aggregates team data.

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, well-structured sentence that efficiently conveys the tool's function without redundancy. It front-loads the core action and details the scope and data types concisely, with no wasted words.

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?

Given the tool's complexity (aggregating team data) and lack of annotations or output schema, the description is minimally adequate. It specifies what data is retrieved but omits behavioral context and output details, leaving the agent with incomplete information for effective use.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately adds no parameter details, focusing instead on the tool's purpose. This meets the baseline for zero-parameter tools.

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 tool's purpose with specific verbs ('Get current status') and resources ('development team'), detailing what information is retrieved (active issues, due items, recent completions per team member). It distinguishes itself from siblings by focusing on team-wide status rather than individual schedules or analysis, though it doesn't explicitly name alternatives.

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 explicit guidance is provided on when to use this tool versus alternatives like analyze_workload or get_person_schedule. The description implies usage for team status overviews but lacks context on prerequisites, timing, or exclusions, leaving the agent to infer appropriate scenarios.

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/blackgirlbytes/github-calendar-mcp-server'

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