Skip to main content
Glama
dappros

Ethora MCP Server

by dappros

ethora-app-update

Modify application details for the logged-in user, including display name, domain, description, color, and bot status, directly within the Ethora MCP Server platform.

Instructions

Updates the application fields for the logged-in user who has created the app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appDescriptionNoSet the application description
appIdYesappId for app
botStatusYesSet the bot status to on or off, if on bot is enabled
displayNameNodisplayName of the application
domainNameNoIf the domainName is set to 'abcd', your web application will be available at abcd.ethora.com.
primaryColorNoSet thie color of the application in #F54927 format

Implementation Reference

  • The handler function for the 'ethora-app-update' MCP tool. It conditionally builds a changes object from optional input parameters and calls the appUpdate API function, returning the result or error.
    async function ({ appId, displayName, domainName, appDescription, primaryColor, botStatus }) {
        try {
            let changes: any = {}
    
            if (displayName) {
                changes.displayName = displayName
            }
            if (domainName) {
                changes.domainName = domainName
            }
            if (appDescription) {
                changes.appDescription = appDescription
            }
            if (primaryColor) {
                changes.primaryColor = primaryColor
            }
            if (botStatus) {
                changes.botStatus = botStatus
            }
            let result = await appUpdate(appId, changes)
            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
        }
    }
  • Zod input schema defining the parameters for the 'ethora-app-update' tool: required appId and optional fields for updating app properties.
    inputSchema: { 
        appId: z.string().describe("appId for app"),
        displayName: z.string().optional().describe("displayName of the application"),
        domainName: z.string().optional().describe("If the domainName is set to 'abcd', your web application will be available at abcd.ethora.com."),
        appDescription: z.string().optional().describe("Set the application description"),
        primaryColor: z.string().optional().describe("Set thie color of the application in #F54927 format"),
        botStatus: z.enum(["on", "off"]).describe("Set the bot status to on or off, if on bot is enabled")
    }
  • src/tools.ts:138-150 (registration)
    Registration of the 'ethora-app-update' tool using server.registerTool, including description and input schema.
    server.registerTool(
        'ethora-app-update',
        {
            description: 'Updates the application fields for the logged-in user who has created the app.',
            inputSchema: { 
                appId: z.string().describe("appId for app"),
                displayName: z.string().optional().describe("displayName of the application"),
                domainName: z.string().optional().describe("If the domainName is set to 'abcd', your web application will be available at abcd.ethora.com."),
                appDescription: z.string().optional().describe("Set the application description"),
                primaryColor: z.string().optional().describe("Set thie color of the application in #F54927 format"),
                botStatus: z.enum(["on", "off"]).describe("Set the bot status to on or off, if on bot is enabled")
            }
        },
  • Helper function appUpdate that makes the HTTP PUT request to update the app via the API client.
    export function appUpdate(appId: string, changes: any) {
      return httpClientDappros.put(
        `/apps/${appId}`,
        changes
      )
    }
  • src/index.ts:13-13 (registration)
    Top-level call to registerTools which includes registration of 'ethora-app-update'.
    registerTools(server);
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 states this is an update operation, implying mutation, but doesn't cover permissions needed, whether changes are reversible, rate limits, or what the response looks like. This is inadequate for a mutation tool with zero annotation coverage.

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

Conciseness4/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 purpose without unnecessary words. It's appropriately sized and front-loaded, though it could be slightly more informative given the lack of annotations.

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 6 parameters, no annotations, and no output schema, the description is insufficient. It lacks details on behavioral traits, error handling, or return values, leaving significant gaps for an AI agent to understand how to use this tool effectively.

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 documents all parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema, such as formatting details or usage examples, 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 verb 'updates' and the resource 'application fields', specifying it's for the logged-in user who created the app. However, it doesn't explicitly differentiate from sibling tools like 'ethora-app-create' or 'ethora-app-delete' beyond the update action.

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 mentions it's for the logged-in user who created the app, providing some context, but offers no explicit guidance on when to use this tool versus alternatives like 'ethora-app-create' or 'ethora-app-delete', nor any prerequisites or exclusions.

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