Skip to main content
Glama
dappros

Ethora MCP Server

by dappros

ethora-app-create

Create a new app on the Ethora MCP Server by specifying a display name, enabling app management and integration with the Ethora platform for user authentication and registration.

Instructions

Create a new app for the logged-in user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
displayNameYesdisplay name for app

Implementation Reference

  • src/tools.ts:89-111 (registration)
    Full registration block for the 'ethora-app-create' MCP tool, including description, input schema (displayName: string), and inline handler function that invokes appCreate API and formats response.
    function appCreateTool(server: McpServer) {
        server.registerTool(
            'ethora-app-create',
            {
                description: 'Create a new app for the logged-in user.',
                inputSchema: { displayName: z.string().describe("display name for app") }
            },
            async function ({ displayName }) {
                try {
                    let result = await appCreate(displayName)
                    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 appCreate that performs the actual HTTP POST request to create an app with the given displayName using the configured axios client.
    export function appCreate(displayName: string) {
      return httpClientDappros.post(
        `/apps/`,
        {
          displayName
        }
      )
    }
  • src/tools.ts:343-343 (registration)
    Invocation of appCreateTool registration within the main registerTools function.
    appCreateTool(server);
  • src/index.ts:13-13 (registration)
    Main server initialization calls registerTools to register all tools including ethora-app-create.
    registerTools(server);
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states this creates an app but doesn't disclose what 'app' means in this context, whether creation is irreversible, what permissions are required, or what happens after creation. For a mutation tool with zero annotation coverage, this is inadequate.

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 with no wasted words. It's appropriately sized for a simple creation tool and front-loads the essential information.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what an 'app' is in this system, what the creation entails, what permissions are needed, or what the result looks like. Given the complexity of app creation and lack of structured data, more context is needed.

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?

Schema description coverage is 100%, so the schema already fully documents the single 'displayName' parameter. The description adds no additional parameter context beyond what the schema provides, 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 ('Create') and resource ('new app'), specifying it's for the logged-in user. However, it doesn't differentiate from sibling 'ethora-app-create-chat', which appears to be a similar creation tool with chat-specific functionality.

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?

No guidance is provided on when to use this tool versus alternatives like 'ethora-app-create-chat' or 'ethora-app-update'. The description mentions it's for the logged-in user, but doesn't specify prerequisites, permissions needed, or contextual constraints.

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