Skip to main content
Glama
dappros

Ethora MCP Server

by dappros

ethora-user-login

Authenticate users on the Ethora platform by logging in with email and password. Simplifies user access and integrates with Ethora MCP Server for application management.

Instructions

Login to Ethora with email and password

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesemail for login
passwordYespassword for login

Implementation Reference

  • The asynchronous handler function for the 'ethora-user-login' tool. It calls the userLogin helper, stringifies the result data, and handles errors by returning a standardized tool response.
        async function ({ email, password }) {
            try {
                let result = await userLogin(email, password)
                let toolRes: CallToolResult = {
                    content: [{ type: "text", text: JSON.stringify(result.data) }]
                }
                return toolRes
            } catch (error) {
                let toolRes: CallToolResult = {
                    content: [{ type: "text", text: "error: network error" }]
                }
                return toolRes
            }
        }
    )
  • Input schema definition for the 'ethora-user-login' tool using Zod, validating email and password parameters.
    {
        description: 'Login to Ethora with email and password',
        inputSchema: { email: z.string().email().describe("email for login"), password: z.string().describe("password for login") }
    },
  • src/tools.ts:6-28 (registration)
    The userLoginWithEmailTool function that registers the 'ethora-user-login' tool on the MCP server, including schema and handler. This function is invoked in registerTools(server).
    function userLoginWithEmailTool(server: McpServer) {
        server.registerTool(
            'ethora-user-login',
            {
                description: 'Login to Ethora with email and password',
                inputSchema: { email: z.string().email().describe("email for login"), password: z.string().describe("password for login") }
            },
            async function ({ email, password }) {
                try {
                    let result = await userLogin(email, password)
                    let toolRes: CallToolResult = {
                        content: [{ type: "text", text: JSON.stringify(result.data) }]
                    }
                    return toolRes
                } catch (error) {
                    let toolRes: CallToolResult = {
                        content: [{ type: "text", text: "error: network error" }]
                    }
                    return toolRes
                }
            }
        )
    }
  • Helper function performing the actual HTTP POST request to '/users/login-with-email' endpoint, extracts and sets authentication tokens, returns the response. Invoked by the tool handler.
    export async function userLogin(email: string, password: string) {
      let resp = await httpClientDappros.post(
        `/users/login-with-email`,
        {
          email,
          password,
        }
      )
      let data = resp.data
      httpTokens.token = data.token
      httpTokens.refreshToken = data.refreshToken
      return resp
    }
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 mentions authentication ('Login') but doesn't specify what happens upon login (e.g., session creation, token return, error handling for invalid credentials). For a security-sensitive tool, this lack of detail 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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core action, making it easy to parse quickly.

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 login operation (involving authentication, potential session management, and error cases), the description is insufficient. With no annotations and no output schema, it fails to explain what the tool returns (e.g., a token, user data) or behavioral aspects like rate limits or security requirements, leaving critical gaps for an AI agent.

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 adds minimal semantic context beyond the input schema, which already has 100% coverage with clear descriptions for 'email' and 'password'. It implies these parameters are for authentication but doesn't provide additional details like format constraints or security considerations, meeting the baseline for high schema coverage.

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 action ('Login to Ethora') and the mechanism ('with email and password'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'ethora-user-register', which likely also involves user credentials but for a different purpose.

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 like 'ethora-user-register' for account creation, nor does it mention prerequisites (e.g., needing an existing account) or exclusions. It simply states what the tool does without contextual usage information.

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