Skip to main content
Glama

ethora-mcp-server

by io.github.dappros
OverviewDiscussionsAdmin

Update Legacy Bot

ethora-bot-update-v2
Idempotent

Configure the AI bot for an app — prompt, LLM, trigger, greeting, RAG behavior, identity, and public widget settings. Partial update — omitted fields are left unchanged. status: "on" activates the bot (best-effort; needs a prompt + LLM and a backend AI service). Auth: app-token mode OR B2B mode with an explicit appId. Errors: 401/403 wrong auth; 404 unknown appId; 422 validation (e.g. an llmProvider/llmModel not enabled). Related: ethora-bot-get-v2, ethora-agents-activate-v2.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdNo24-char hex appId. Required in B2B mode unless already set via `ethora-app-select`; ignored in app-token mode.
isRAGNoIf true, the bot retrieves from the app's indexed RAG sources (see the `ethora-sources-*` tools) when answering.
chatIdNoRestrict the bot to a single chat by id. Omit to apply app-wide.
promptNoSystem prompt that defines the bot's persona and behavior.
statusNo`on` activates the bot, `off` deactivates it. Omit to leave the current status unchanged.
ragTagsNoRestrict RAG retrieval to sources tagged with these tags (see `ethora-sources-site-tags-update-v2` / `ethora-sources-docs-tags-update-v2`).
triggerNoWhen the bot responds: `any_message` (replies to every message) or `/bot` (only messages starting with /bot).
llmModelNoLLM model id, e.g. `gpt-4o-mini`. Must be available for the chosen `llmProvider`.
botLastNameNoBot's last name in its user profile.
llmProviderNoLLM provider, e.g. `openai` or `openai-compatible`. Must be enabled in your Ethora backend's AI service config.
botAvatarUrlNoPublic URL of the bot's avatar image.
botFirstNameNoBot's first name in its user profile.
savedAgentIdNoId of a saved agent whose config should back this bot. Alternative to setting prompt/LLM/RAG fields individually.
botDisplayNameNoBot's display name shown in chat.
greetingMessageNoMessage the bot posts when a conversation starts.
widgetPublicUrlNoPublic URL for the embeddable widget. Usually read via `ethora-bot-widget-v2` rather than set here.
widgetPublicEnabledNoIf true, expose the bot through a public embeddable chat widget.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond annotations (which already signal write/idempotent/non-destructive), the description discloses omitted fields are unchanged, activation is best-effort and depends on a prompt, LLM, and backend AI service, and enumerates auth/error behavior. This is unusually transparent.

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?

Four compact sentences front-load the purpose and partial-update behavior, then cover activation, auth/errors, and related tools. No filler or repetition of schema details.

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 17-optional-param update tool with no output schema, the description plus schema gives everything needed to select and invoke it: purpose, update semantics, activation requirements, auth modes, failure modes, and related tools.

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%, so the baseline is 3; the description adds real cross-parameter meaning: omitted fields are left unchanged, `status:'on'` requires a prompt/LLM/backend service, and `appId` behaves differently by auth mode. It does not enumerate all 17 fields, but the schema already does that.

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 states a specific action and target ('Configure the AI bot for an app') and lists the setting categories, so an agent can tell it from read-only bot tools. It stays at 4 rather than 5 because it does not explicitly differentiate from ethora-agents-update-v2 or explain the legacy-bot vs agents distinction.

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 gives clear invocation context: partial update, when `status: 'on'` is viable, the two auth modes, and common error cases. It stops short of explicit when-to-use vs alternative tools, only naming related tools without conditions.

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

All ethora-mcp-server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources