Skip to main content
Glama
dappros

Ethora MCP Server

by dappros

ethora-app-create-chat

Enable users to create new chats within their applications, specifying app IDs, chat titles, and pin preferences for organized communication.

Instructions

Create a new chat for the logged-in user who has created the app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesappId for app
pinnedYespinned for chat
titleYestitle for chat

Implementation Reference

  • src/tools.ts:234-260 (registration)
    Registration of the 'ethora-app-create-chat' tool including schema definition and handler function that invokes the API to create a chat.
    function craeteAppChatTool(server: McpServer) {
        server.registerTool(
            'ethora-app-create-chat',
            {
                description: 'Create a new chat for the logged-in user who has created the app.',
                inputSchema: {
                    appId: z.string().describe("appId for app"),
                    title: z.string().describe("title for chat"),
                    pinned: z.boolean().describe("pinned for chat"),
                }
            },
            async function ({ appId, title, pinned }) {
                try {
                    let result = await appCreateChat(appId, title, pinned)
                    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
                }
            }
        )
    }
  • The core handler function for the ethora-app-create-chat tool, which calls appCreateChat and formats the response.
    async function ({ appId, title, pinned }) {
        try {
            let result = await appCreateChat(appId, title, pinned)
            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 and description for the ethora-app-create-chat tool using Zod.
    {
        description: 'Create a new chat for the logged-in user who has created the app.',
        inputSchema: {
            appId: z.string().describe("appId for app"),
            title: z.string().describe("title for chat"),
            pinned: z.boolean().describe("pinned for chat"),
        }
    },
  • Helper function appCreateChat that performs the HTTP POST request to create the chat via the API endpoint.
    export function appCreateChat(appId: string, title: string, pinned: boolean) {
      return httpClientDappros.post(
        `/apps/create-app-chat/${appId}`,
        {
          title,
          pinned
        }
      )
    }
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 the tool creates a chat, implying a mutation, but does not cover critical aspects like authentication requirements, error handling, rate limits, or what happens upon creation (e.g., response format). This leaves significant gaps in understanding the tool's behavior.

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 purpose without unnecessary words. It is front-loaded with the key action and context, making it easy to parse and understand 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 tool's complexity as a mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits, return values, and usage context, leaving the agent with incomplete information to effectively invoke the tool. More context is needed to meet minimum viability for such operations.

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 schema description coverage is 100%, with clear descriptions for each parameter (appId, pinned, title). The description does not add any additional meaning beyond what the schema provides, such as explaining the purpose of 'pinned' or constraints on 'title'. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 a new chat') and the resource ('for the logged-in user who has created the app'), making the purpose understandable. However, it does not explicitly differentiate this tool from sibling tools like 'ethora-app-create' or 'ethora-app-delete-chat', which would be needed for a score of 5.

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, such as other chat-related tools in the sibling list. It mentions the user context ('logged-in user who has created the app'), but this is more of a prerequisite than usage guidance, leaving the agent without clear direction on tool selection.

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