Skip to main content
Glama
aic0t

AI Coach MCP Server

by aic0t
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Show a message on the mascot

show_ai_coach_message

Show short plain text in the AI Coach mascot's speech bubble so the desktop pet reacts to the conversation. Display care prompts or messages without images or links.

Instructions

Display a short text (up to 140 characters) in the AI Coach mascot's speech bubble. Text only; no images or links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText to show in the speech bubble (up to 140 characters, plain text only).
localeNoDisplay language (BCP 47).
mascotIdNoA mascotId returned by status. Defaults to the primary mascot when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.4
    • changedInput schema / properties / locale / description
      Previous value: -"Display language hint (BCP 47). The dashboard view passes hostContext.locale through unchanged."New value: +"Display language (BCP 47)."
    • changedInput schema / properties / text / description
      Previous value: -"Text to show in the speech bubble. Up to 140 Unicode scalars and 560 UTF-8 bytes, no control characters."New value: +"Text to show in the speech bubble (up to 140 characters, plain text only)."
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "connection": {
-      "enum": [
-        "connected",
-        "app_unavailable",
-        "incompatible"
-      ],
-      "type": "string"
-    },
-    "displayDurationSeconds": {
-      "type": "number"
-    },
-    "error": {
-      "additionalProperties": false,
-      "properties": {
-        "code": {
-          "type": "string"
-        },
-        "reason": {
-          "type": "string"
-        },
-        "retryable": {
-          "type": "boolean"
-        }
-      },
-      "required": [
-        "code",
-        "retryable"
-      ],
-      "type": "object"
-    },
-    "mascotId": {
-      "type": "string"
-    },
-    "protocolVersion": {
-      "const": 1,
-      "type": "number"
-    },
-    "shown": {
-      "type": "boolean"
-    },
-    "updatedAt": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "protocolVersion",
-    "connection",
-    "shown",
-    "updatedAt"
-  ],
-  "type": "object"
-}New value: +null
  2. First observedv0.1.2

TDQS

A3.8/5.0
Behavior3/5

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

The description characterizes the action as displaying transient UI content in the mascot's speech bubble, and annotations already indicate non-read-only and non-destructive behavior. It adds the 140-character limit and plain-text restriction, but it does not clarify whether the message replaces an existing one or auto-dismisses.

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 only two sentences long, with the core action and the key limit front-loaded in the first sentence. The second sentence earns its place by ruling out images and links, leaving no filler or repetition.

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 simple display tool with one required parameter, the description covers the essential information: what to display, where to display it, and what content is not allowed. The locale and mascotId behavior is fully described in the schema, and the annotations cover the safety profile, so only minor behavioral details such as message replacement or auto-dismissal are missing.

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 schema already documents all three parameters—text, locale, and mascotId—with meaningful descriptions, and the context signals report 100% schema description coverage. The tool description only restates the 140-character plain-text constraint for text, adding no substantial semantic value beyond the schema.

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 uses the specific verb 'Display', identifies the exact resource ('the AI Coach mascot's speech bubble'), and scopes the action to a short text of up to 140 characters. The closing 'Text only; no images or links' helps distinguish this tool from sibling display tools like show_ai_coach_file and show_ai_coach_git_graph.

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

Usage Guidelines3/5

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

The description implies appropriate usage through constraints like 'short text' and 'Text only; no images or links', which tells an agent this tool is not for media content. However, it never explicitly names alternatives or states when to choose this tool over a sibling, so the guidance remains implicit.

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