Skip to main content
Glama
dappros

Ethora MCP Server

by dappros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Default Rooms for App

ethora-app-get-default-rooms-with-app-id
Read-only

Retrieve default chat rooms for an Ethora app using its app ID. Returns room JIDs and titles for the specified app.

Instructions

List the default chat rooms of a specific Ethora app, passed via appId (or the currently selected app). Returns rooms with their JIDs and titles. Requires: an appId from ethora-app-list or ethora-app-create. Auth: user-auth mode, active session; the caller needs read access (ownership or room membership). Errors: 400 no appId and none selected; 401 not logged in; 403 no read access; 404 unknown appId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdNo24-char hex ObjectId of the app whose default rooms you want to read. Optional — defaults to the app most recently passed to `ethora-app-select`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv26.9.3
    • changedInput schema / properties / appId / description
      Previous value: -"appId for app"New value: +"24-char hex ObjectId of the app whose default rooms you want to read. Optional — defaults to the app most recently passed to `ethora-app-select`."
    • removedInput schema / required
      Removed value: -[
-  "appId"
-]
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this as read-only and non-destructive; the description adds useful behavioral context: return content (rooms with JIDs/titles), auth mode, and specific error conditions (400/401/403/404). No contradiction with annotations.

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 main intent is front-loaded in the first sentence, and the supporting requirements/auth/errors are compactly grouped. Each block earns its place, though the error-code enumeration could arguably be trimmed without losing essential guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-optional-parameter read tool with no output schema, the description covers the input source, auth prerequisites, failure modes, and the key return fields. The only notable gap is the absence of an explicit distinction from the closely related sibling tool.

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?

Schema coverage is 100% and the schema already documents the optional `appId` and its 24-char hex format and default behavior. The description adds provenance guidance (where to obtain a valid `appId`) and reinforces the selected-app fallback, which is valuable beyond the schema.

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 names a specific verb ('List') and resource ('default chat rooms of a specific Ethora app'), with a clear scoping mechanism (`appId` or currently selected app). It does not explicitly contrast with the similarly named sibling `ethora-app-get-default-rooms`, so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the caller to obtain `appId` from `ethora-app-list` or `ethora-app-create`, states that it may also use the currently selected app, and lists authentication/read-access requirements. It provides clear context but no explicit 'when not to use' or alternative routing versus the sibling tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools