Skip to main content
Glama
dappros

Ethora MCP Server

by dappros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update App

ethora-app-update
Idempotent

Update app settings like display name, domain, tagline, color, or bot status for an Ethora app you own. Partial update; requires appId.

Instructions

Update mutable fields on an app the caller owns (displayName, domainName, appTagline, primaryColor, botStatus). Partial update — omitted fields are left unchanged. Requires: an appId from ethora-app-list or ethora-app-create. Auth: user-auth mode, active session; the caller must own the app. Errors: 401 not logged in; 403 not owner; 404 unknown appId; 422 validation (e.g. domainName taken, primaryColor not #RRGGBB).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdNo24-char hex ObjectId of the app to update. Optional — defaults to the app most recently passed to `ethora-app-select`.
botStatusNo`on` enables the AI bot for new conversations (requires a configured prompt — see `ethora-bot-update-v2`); `off` disables it. Does not change the bot's configured prompt or sources.
appTaglineNoShort tagline shown on the public app landing page.
domainNameNoSubdomain to host the web app at. Setting `abcd` makes the web app available at `abcd.ethora.com`. Must be unique across all Ethora apps; lower-case alphanumerics and dashes only.
displayNameNoNew human-readable app name. Visible in the app picker and on the public landing page.
primaryColorNoPrimary brand color in hex `#RRGGBB` format (e.g. `#F54927`). Used throughout the app UI.
appDescriptionNoDeprecated alias for `appTagline`, kept so older callers keep working. Prefer `appTagline`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv26.9.3
    • changedInput schema / properties / appDescription / description
      Previous value: -"Set the application description"New value: +"Deprecated alias for `appTagline`, kept so older callers keep working. Prefer `appTagline`."
    • changedInput schema / properties / appId / description
      Previous value: -"appId for app"New value: +"24-char hex ObjectId of the app to update. Optional — defaults to the app most recently passed to `ethora-app-select`."
    • addedInput schema / properties / appTagline
      Added value: +{
+  "description": "Short tagline shown on the public app landing page.",
+  "type": "string"
+}
    • changedInput schema / properties / botStatus / description
      Previous value: -"Set the bot status to on or off, if on bot is enabled"New value: +"`on` enables the AI bot for new conversations (requires a configured prompt — see `ethora-bot-update-v2`); `off` disables it. Does not change the bot's configured prompt or sources."
    • changedInput schema / properties / displayName / description
      Previous value: -"displayName of the application"New value: +"New human-readable app name. Visible in the app picker and on the public landing page."
    • changedInput schema / properties / domainName / description
      Previous value: -"If the domainName is set to 'abcd', your web application will be available at abcd.ethora.com."New value: +"Subdomain to host the web app at. Setting `abcd` makes the web app available at `abcd.ethora.com`. Must be unique across all Ethora apps; lower-case alphanumerics and dashes only."
    • changedInput schema / properties / primaryColor / description
      Previous value: -"Set thie color of the application in #F54927 format"New value: +"Primary brand color in hex `#RRGGBB` format (e.g. `#F54927`). Used throughout the app UI."
    • removedInput schema / required
      Removed value: -[
-  "appId",
-  "botStatus"
-]
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds valuable behavioral context beyond the annotations: partial-update semantics ('omitted fields are left unchanged'), the ownership requirement, and the specific error conditions. It also clarifies that botStatus changes do not alter the bot's configured prompt or sources. The only minor gap is that it doesn't describe the response body, but with no output schema and a mutation tool, the error/ownership context is the more important behavioral disclosure.

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 compact and front-loaded: the first sentence states the action and scope, the second states the partial-update semantics, and the remaining lines pack prerequisites, auth, and errors into a scannable block. Every sentence earns its place; there is no filler or repetition of schema content.

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

Completeness5/5

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

For a mutation tool with 7 parameters, full schema coverage, and no output schema, the description covers everything an agent needs to call it correctly: what fields can be updated, partial-update behavior, how to obtain the appId, auth requirements, ownership, and error semantics. The sibling list includes create/delete/select tools, and the description explicitly routes the agent to the right source for appId. Nothing critical is missing.

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 description coverage is 100%, so the schema already documents every parameter. The description adds meaning beyond the schema by naming the core mutable fields up front, explaining the partial-update behavior, and clarifying the appId default ('defaults to the app most recently passed to ethora-app-select'). It also flags appDescription as a deprecated alias, which is not obvious from the schema alone. The description doesn't repeat every schema detail, which is appropriate given full coverage.

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

Purpose5/5

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

The description opens with a specific verb ('Update') and resource ('mutable fields on an app the caller owns'), then enumerates the exact fields (displayName, domainName, appTagline, primaryColor, botStatus). It also states the partial-update semantics, which distinguishes it from create/delete siblings. An agent can tell this apart from ethora-app-create and ethora-app-delete without opening the schema.

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

Usage Guidelines5/5

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

The description explicitly states the prerequisite ('Requires: an appId from ethora-app-list or ethora-app-create'), the auth mode ('user-auth mode, active session'), and the ownership condition ('the caller must own the app'). It also enumerates the error conditions (401/403/404/422), which tells the agent when the call will fail and how to react. This is explicit when-to-use guidance with no ambiguity.

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