Function registerTools

packages/mcp/src/tools-definition.js:55–855

(server)

 * @param {McpServer} server - The MCP server instance to register tools on
 */
export function registerTools(server) {
  // Helper functions for dynamic date generation
  const getNow = () => new Date()
  const getThreeHoursAgo = () => new Date(Date.now() - 3 * 60 * 60 * 1000)
  const getTwentyFourHoursAgo = () => new Date(Date.now() - 24 * 60 * 60 * 1000)
  const getFifteenMinutesAgo = () => new Date(Date.now() - 15 * 60 * 1000)

  // Get today's date in ISO format for examples
  const getTodayDate = () => {
    const today = new Date()
    // Return the full ISO string which includes the correct timezone (Z indicates UTC)
    return today.toISOString()
  }

  // Today's date for AI to reference
  const todayDate = getTodayDate()

  // Register the resources listing tool for debugging serverless applications
  server.tool(
    'list-resources',
    '⚠️ MANDATORY PREREQUISITE: You MUST ALWAYS run the list-projects tool FIRST before using this tool! ⚠️\n\n' +
      'Lists all cloud resources associated with a serverless service.\n\n' +
      'REQUIRED WORKFLOW:\n' +
      '1. FIRST: Run the list-projects tool to identify all serverless projects in the workspace\n' +
      '2. If multiple projects are found, explicitly ask the user which project to use\n' +
      '3. ALWAYS confirm with the user which service they want information about, even if only one project is found\n' +
      "4. NEVER assume which service the user is interested in - if it is not completely clear from the user's request, you MUST ask for clarification\n" +
      '5. Check if stage, region, and profile are specified in the service configuration - if found, USE THESE VALUES in subsequent tool requests\n' +
      '6. ONLY THEN use this list-resources tool with the confirmed project information\n\n' +
      AWS_CREDENTIALS_ERROR_HANDLING +
      '\n\n' +
      'This tool adapts to different infrastructure types: for Serverless Framework or CloudFormation services, it queries the actual deployed resources; for Terraform projects, it provides instructions on how to list resources using terraform state commands. This tool helps identify specific resources (Lambda functions, IAM roles, etc.) that you can then investigate in detail with other specialized tools.',
    {
      serviceName: z
        .string()
        .describe(
          '⚠️ SERVICE NAME REQUIREMENTS BY PROJECT TYPE ⚠️\n\n' +
            '=== FOR SERVERLESS FRAMEWORK PROJECTS ===\n' +
            '• FORMAT: "serviceName-stageName" (REQUIRED)\n' +
            '• EXAMPLES:\n' +
            '  ✓ CORRECT: "my-service-dev", "superapp-platform-prod"\n' +
            '  ✗ INCORRECT: "superapp-platform" (missing stage)\n' +
            '• The stage name (e.g., "dev", "prod", "staging") MUST be included\n\n' +
            'HOW TO FIND THE STAGE NAME:\n' +
            '1. Open the serverless.yml file for the project\n' +
            '2. Look for provider.stage in the file (e.g., provider: { stage: "dev" })\n' +
            '3. If provider.stage is not specified, use "dev" (the default)\n' +
            '4. If you cannot determine the stage, ask the user which stage to check\n\n' +
            '=== FOR CLOUDFORMATION PROJECTS ===\n' +
            '• You MUST ask the user for the exact CloudFormation stack name\n' +
            '• CloudFormation stack names are case-sensitive\n' +
            '• Example: "my-application-stack"\n\n' +
            '=== FOR TERRAFORM PROJECTS ===\n' +
            '• Provide the name of the Terraform project\n' +
            '• Example: "my-terraform-project"\n\n' +
            'ALWAYS ask for clarification if you are unsure which service name to use.',
        ),
      serviceType: z