Skip to main content
Glama
dappros

Ethora MCP Server

by dappros

ethora-app-get-default-rooms

Retrieve default rooms for the Ethora application using the Ethora MCP Server. Simplifies integration by providing essential room data for application setup and management.

Instructions

Get the default rooms for Ethora application

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools.ts:185-206 (registration)
    Registration of the 'ethora-app-get-default-rooms' MCP tool, including schema (no input params) and inline handler that calls the API helper and returns JSON response.
    function appGetDefaultRoomsTool(server: McpServer) {
        server.registerTool(
            'ethora-app-get-default-rooms',
            {
                description: 'Get the default rooms for Ethora application',
            },
            async function () {
                try {
                    let result = await appGetDefaultRooms()
                    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
                }
            }
        )
    }
  • API client helper function that makes the GET request to retrieve the default rooms for Ethora application.
    export function appGetDefaultRooms() {
      return httpClientDappros.get(
        `/apps/get-default-rooms`
      )
    }
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 'Get' implies a read operation, but doesn't specify whether this requires authentication, what the return format is (e.g., list of rooms, JSON structure), or any rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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 with no wasted words. It's front-loaded with the core action ('Get the default rooms') and specifies the context ('for Ethora application'). Every part of the sentence contributes to understanding the tool's purpose.

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 low complexity (0 parameters) but lack of annotations and output schema, the description is incomplete. It doesn't explain what 'default rooms' are, how they're returned, or any behavioral traits. For a tool that likely returns data, more context on the output would be helpful, especially since there's no output schema provided.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics, so it meets the baseline of 4 for tools with no parameters. It correctly implies no inputs are required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose ('Get the default rooms for Ethora application'), which is clear but vague. It specifies the verb 'Get' and resource 'default rooms', but doesn't distinguish it from its sibling 'ethora-app-get-default-rooms-with-app-id' or explain what 'default rooms' means in this context. The purpose is understandable but lacks specificity.

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. It doesn't mention its sibling 'ethora-app-get-default-rooms-with-app-id' (which likely requires an app ID parameter) or other related tools like 'ethora-app-list'. The description offers no context on prerequisites, exclusions, or typical use cases.

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