Skip to main content
Glama
dappros

Ethora MCP Server

by dappros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create App

ethora-app-create

Create a new Ethora app (tenant) for the logged-in user. Provide a display name to get a fresh appId and owner access, subject to your plan limit.

Instructions

Create a new Ethora app (tenant) owned by the currently logged-in user. Allocates a fresh 24-char hex appId and sets the caller as owner; counts against the owner's plan limit. Returns the new app object including appId. The returned app has its credential fields redacted; call ethora-app-credentials { appId, confirm: true } when a snippet needs the appToken. Auth: user-auth mode, active session (ethora-user-login first). Errors: 401 not logged in; 402/403 plan limit reached; 422 invalid displayName. Related: server-side provisioning uses ethora-b2b-app-create.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
displayNameYesHuman-readable app name shown to users in the app picker and on the public landing page. Not required to be unique across accounts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv26.9.3
    • changedInput schema / properties / displayName / description
      Previous value: -"display name for app"New value: +"Human-readable app name shown to users in the app picker and on the public landing page. Not required to be unique across accounts."
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the tool allocates a fresh appId, sets the caller as owner, counts against the plan limit, returns an app object, and redacts credential fields. These are meaningful behavioral disclosures that help an agent predict side effects and response content.

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 dense but every sentence carries operational value: purpose, side effects, return behavior, credential redaction, auth, errors, and related tool. It is front-loaded with the core purpose and structured logically.

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 single-parameter creation tool with no output schema, the description covers prerequisites, return shape, redacted fields, error codes, plan-limit side effects, and the relevant alternative tool. There is no critical missing information an agent would need to call it correctly.

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 input schema already fully documents displayName with a clear description and uniqueness caveat (100% coverage). The description only adds a marginal hint that an invalid displayName yields a 422 error, which does not substantially extend the schema semantics.

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 action and resource: 'Create a new Ethora app (tenant) owned by the currently logged-in user.' It also differentiates from the related server-side provisioning path by naming ethora-b2b-app-create, making its scope unambiguous.

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?

It gives explicit prerequisites (user-auth mode, ethora-user-login first), error conditions that inform when the call will fail, and directs the agent to ethora-app-credentials when an appToken is needed and to ethora-b2b-app-create for server-side provisioning. This is strong when-to-use guidance.

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