TeamRetro MCP Server

Instructions

Implementation Reference

• src/features/teams/tools.ts:30-35 (handler)

  Primary definition and handler for the 'detail_team' tool. Includes input schema (requiring team ID), description, and async handler that invokes teamsService.getTeam to fetch team details.
  detail_team: { schema: teamSchema.pick({ id: true }), description: "Retrieve detailed information about a single team by its unique ID", handler: async (args: { id: string }) => createToolResponse(teamsService.getTeam(args.id)), },
• src/features/teams/service.ts:34-36 (helper)

  Supporting service method that executes the core logic: HTTP GET request to the /v1/teams/{id} API endpoint to retrieve detailed team information.
  async getTeam(teamId: string): Promise<SingleApiResponse<Team>> { return this.get<SingleApiResponse<Team>>(`/v1/teams/${teamId}`); }
• src/tools.ts:13-22 (registration)

  Global registration of feature tools, including teamTools containing 'detail_team', by spreading into the main tools object for schema generation and handler mapping.
  const tools = { ...userTools, ...teamTools, ...teamMembersTools, ...actionTools, ...retrospectiveTools, ...agreementTools, ...healthModelTools, ...healthCheckTools, };
• src/features/teams/tools.ts:31-31 (schema)

  Input schema for detail_team tool: Zod schema picking only the 'id' field from teamSchema for validation.
  schema: teamSchema.pick({ id: true }),
• src/tools.ts:15-15 (registration)

  Specific inclusion of teamTools (with detail_team) in the main tools registry.
  ...teamTools,