Skip to main content
Glama
dappros

Ethora MCP Server

by dappros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Legacy Bot Widget

ethora-bot-widget-v2
Read-only

Fetches the legacy bot widget config for apps with a dashboard-created aiBot. For API-created apps, use the widget embed snippet instead.

Instructions

LEGACY: read the per-app bot widget config (GET /v2/bot/widget); only apps that already have a legacy aiBot have one, API-created apps get 422. For the embeddable AI chat widget use ethora-widget-embed-snippet instead — the widget config and public widget URL metadata needed to embed the bot on a website. Requires: an app with a legacy per-app aiBot (dashboard-created). API-created apps have none: use ethora-agents-create-v2 -> ethora-agent-invite-to-chat -> ethora-agents-activate-v2 instead. Auth: app-token mode (after ethora-app-select + ethora-auth-use-app). Errors: 401/403 not in app-token mode or invalid appToken. Related: enable/disable via widgetPublicEnabled in ethora-bot-update-v2.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv26.9.3

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already set readOnlyHint and destructiveHint. Description adds key context: 422 error for API-created apps, auth modes, and that it returns metadata needed for embedding. This exceeds baseline given annotation coverage.

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?

Description is dense but front-loaded with the 'LEGACY' tag and endpoint. Three sentences pack a lot of nuance; could be slightly streamlined but every sentence earns its place.

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 zero-param read tool with no output schema, the description covers purpose, constraints, auth, and relations. Minor gap: doesn't describe exact response structure, but output schema is absent and not required for selection.

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?

Tool has zero parameters, so schema carries no burden. Description clarifies what 'config' means and its purpose (embedding metadata), adding semantic value.

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?

States a specific verb ('read'), resource ('per-app bot widget config'), and endpoint ('GET /v2/bot/widget'). Clearly distinguishes itself as a legacy accessor versus the embeddable widget tool.

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?

Explicitly says when to use it (apps with legacy aiBot), when not to use it (API-created apps get 422), and names the alternative tool (`ethora-widget-embed-snippet`) plus a full workflow for API-created apps. Also specifies auth requirements.

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