Skip to main content
Glama
gitCarrot

AWS Cognito MCP Server

by gitCarrot

confirm_code_from_email_for_signUp

Verify email confirmation codes during user registration to complete AWS Cognito sign-up processes and activate accounts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYes
confirmationCodeYes

Implementation Reference

  • Handler function that creates a CognitoUser and calls confirmRegistration with the provided confirmation code to confirm the signup.
    async ({ username, confirmationCode }) => {
        const cognitoUser = new CognitoUser({
            Username: username,
            Pool: userPool,
        });
    
        return new Promise((resolve, reject) => {
            cognitoUser.confirmRegistration(confirmationCode, true, (err, result) => {
                if (err) {
                    console.error('Error confirming registration:', err);
                    reject({
                        content: [
                            {
                                type: "text" as const,
                                text: `Account confirmation failed: ${err.message}`,
                            },
                            {
                                type: "text" as const,
                                text: `Error code: ${(err as any).code || 'Unknown'}`,
                            }
                        ]
                    });
                } else {
                    console.log('Account confirmed successfully:', result);
                    resolve({
                        content: [
                            {
                                type: "text" as const,
                                text: "Account confirmed successfully",
                            },
                            {
                                type: "text" as const,
                                text: `Username: ${username}`,
                            },
                            {
                                type: "text" as const,
                                text: `Confirmation code: ${confirmationCode.substr(0, 2)}****${confirmationCode.substr(-2)}`,
                            },
                            {
                                type: "text" as const,
                                text: `Result: ${result || 'SUCCESS'}`,
                            },
                            {
                                type: "text" as const,
                                text: `Time: ${new Date().toISOString()}`,
                            }
                        ]
                    });
                }
            });
        });
    }
  • Zod schema defining input parameters: username and confirmationCode.
    {
        username: z.string(),
        confirmationCode: z.string(),
    },
  • index.ts:161-219 (registration)
    Registration of the tool using server.tool() with name, input schema, and handler function.
    server.tool(
        "confirm_code_from_email_for_signUp",
        {
            username: z.string(),
            confirmationCode: z.string(),
        },
        async ({ username, confirmationCode }) => {
            const cognitoUser = new CognitoUser({
                Username: username,
                Pool: userPool,
            });
    
            return new Promise((resolve, reject) => {
                cognitoUser.confirmRegistration(confirmationCode, true, (err, result) => {
                    if (err) {
                        console.error('Error confirming registration:', err);
                        reject({
                            content: [
                                {
                                    type: "text" as const,
                                    text: `Account confirmation failed: ${err.message}`,
                                },
                                {
                                    type: "text" as const,
                                    text: `Error code: ${(err as any).code || 'Unknown'}`,
                                }
                            ]
                        });
                    } else {
                        console.log('Account confirmed successfully:', result);
                        resolve({
                            content: [
                                {
                                    type: "text" as const,
                                    text: "Account confirmed successfully",
                                },
                                {
                                    type: "text" as const,
                                    text: `Username: ${username}`,
                                },
                                {
                                    type: "text" as const,
                                    text: `Confirmation code: ${confirmationCode.substr(0, 2)}****${confirmationCode.substr(-2)}`,
                                },
                                {
                                    type: "text" as const,
                                    text: `Result: ${result || 'SUCCESS'}`,
                                },
                                {
                                    type: "text" as const,
                                    text: `Time: ${new Date().toISOString()}`,
                                }
                            ]
                        });
                    }
                });
            });
        }
    )
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

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?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/gitCarrot/mcp-server-aws-cognito'

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