Skip to main content
Glama
dappros

Ethora MCP Server

by dappros

Ethora registration

ethora-user-register

Register users on Ethora MCP Server by providing email, first name, and last name. Facilitates user authentication and management within the Ethora platform.

Instructions

Ethora registration with email (required), firstName (required), lastName (required)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYes
firstNameYes
lastNameYes

Implementation Reference

  • The complete tool handler and registration for 'ethora-user-register'. Includes inline input schema validation using Zod and the execution logic that calls the userRegistration API helper, handles errors, and returns appropriate responses.
    function userRegisterWithEmailTool(server: McpServer) {
        server.registerTool(
            'ethora-user-register',
            {
                title: 'Ethora registration',
                description: 'Ethora registration with email (required), firstName (required), lastName (required)',
                inputSchema: { email: z.string().email(), firstName: z.string(), lastName: z.string() }
            },
            async function ({ email, firstName, lastName }) {
                try {
                    await userRegistration(email, firstName, lastName)
                } catch (error) {
                    if (error && typeof error === 'object' && 'response' in error) {
                        const axiosError = error as any;
                        if (axiosError.response?.status === 422) {
                            const errorData = axiosError.response.data;
    
                            return {
                                content: [{ type: "text", text: `Error: ${errorData.error}` }]
                            }
                        }
    
                    } else {
                        return {
                            content: [{ type: "text", text: 'An error occurred during user registration.' }]
                        }
                    }
                }
    
                return {
                    content: [{ type: "text", text: `Operation successful. Please follow the link in your email to complete the registration.` }]
                }
            }
        )
    }
  • Input schema for the 'ethora-user-register' tool defining required email, firstName, and lastName with Zod validation.
    {
        title: 'Ethora registration',
        description: 'Ethora registration with email (required), firstName (required), lastName (required)',
        inputSchema: { email: z.string().email(), firstName: z.string(), lastName: z.string() }
    },
  • src/tools.ts:30-64 (registration)
    Registration of the 'ethora-user-register' tool via server.registerTool call within userRegisterWithEmailTool, which is invoked in registerTools.
    function userRegisterWithEmailTool(server: McpServer) {
        server.registerTool(
            'ethora-user-register',
            {
                title: 'Ethora registration',
                description: 'Ethora registration with email (required), firstName (required), lastName (required)',
                inputSchema: { email: z.string().email(), firstName: z.string(), lastName: z.string() }
            },
            async function ({ email, firstName, lastName }) {
                try {
                    await userRegistration(email, firstName, lastName)
                } catch (error) {
                    if (error && typeof error === 'object' && 'response' in error) {
                        const axiosError = error as any;
                        if (axiosError.response?.status === 422) {
                            const errorData = axiosError.response.data;
    
                            return {
                                content: [{ type: "text", text: `Error: ${errorData.error}` }]
                            }
                        }
    
                    } else {
                        return {
                            content: [{ type: "text", text: 'An error occurred during user registration.' }]
                        }
                    }
                }
    
                return {
                    content: [{ type: "text", text: `Operation successful. Please follow the link in your email to complete the registration.` }]
                }
            }
        )
    }
  • Supporting API client function userRegistration that performs the HTTP POST to the backend endpoint for user sign-up.
    export function userRegistration(email: string, firstName: string, lastName: string) {
      return httpClientDappros.post(
        `/users/sign-up-with-email/`,
        {
          email,
          firstName,
          lastName
        }
      )
    }
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 'registration', implying a write operation that creates a new user, but doesn't disclose any behavioral traits like authentication requirements, rate limits, error handling, or what happens upon success (e.g., does it return a user ID or token?). For a mutation tool with zero annotation coverage, this is a significant gap.

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 extremely concise and front-loaded, consisting of a single sentence that directly states the tool's purpose and parameters. There's no wasted text, and every word earns its place by conveying essential information efficiently.

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 complexity of a user registration tool (a write operation with no annotations and no output schema), the description is incomplete. It doesn't explain what the tool returns, error conditions, or behavioral aspects like side effects. With no output schema and zero annotation coverage, the description should do more to compensate, but it only covers basic parameter requirements.

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

Parameters3/5

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

The description lists the parameters (email, firstName, lastName) and marks them as required, which adds meaning beyond the input schema that has 0% description coverage. However, it doesn't provide additional semantics like format hints (e.g., email format is implied but not explained) or constraints beyond what's in the schema. With low schema coverage, this partially compensates but doesn't fully address gaps.

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: 'Ethora registration with email (required), firstName (required), lastName (required)'. It specifies the verb 'registration' and the resource 'Ethora', making the action clear. However, it doesn't explicitly differentiate from sibling tools like 'ethora-user-login', which is a related but distinct operation.

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, such as whether this is for new users only, or how it relates to sibling tools like 'ethora-user-login' for existing users. There's no explicit when/when-not usage context provided.

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

Related 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/dappros/ethora-mcp-cli'

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