Skip to main content
Glama

mu

by mu.micro

Send chat

chat_send

Say something in a discussion room, as the caller. Use chat_rooms to find the room id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomYesRoom id, as returned by chat_rooms
messageYesWhat to say

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • removedInput schema / properties / content
      Removed value: -{
-  "description": "What to say",
-  "type": "string"
-}
    • addedInput schema / properties / message
      Added value: +{
+  "description": "What to say",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "room",
-  "content"
-]New value: +[
+  "room",
+  "message"
+]
  2. Added

TDQS

A3.8/5.0
Behavior2/5

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

With no behavioral annotations provided (no readOnlyHint, destructiveHint), the description must disclose side effects. It implies a write operation via 'Say something', but does not state whether authentication is required, whether the message is permanent, or what happens on success/failure. The only extra context is 'as the caller', which clarifies the message origin, but the description does not fully carry the burden of 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 a single sentence that front-loads the action and immediately gives the prerequisite for the main parameter. Zero waste, and the structure is optimal for a tool with only two parameters.

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?

Given the tool's simplicity (2 params, no output schema, no nested objects), the description sufficiently covers the necessary usage context: what the tool does, how to get the required parameter, and the caller perspective. It lacks a mention of return value, but that is standard for send operations and not critical. The description is complete enough for correct invocation.

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 covers 100% of parameters, so each property has a description. The tool description adds the valuable hint that 'room' is obtained from chat_rooms, which is beyond the schema's generic 'Room id'. This aids parameter usage, but the core semantics of the parameters are already in the schema, so the baseline of 3 applies.

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 clearly states the action ('Say something in a discussion room, as the caller'), identifying the verb (send/say) and resource (chat message). It is distinguishable from sibling tools like chat_messages (which likely reads messages) and chat_rooms (which lists rooms). The phrase 'as the caller' adds precision about who sends the message.

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?

The description provides an explicit prerequisite: 'Use chat_rooms to find the room id'. This tells the agent how to satisfy the 'room' parameter. However, it does not explicitly mention when to use this tool versus alternatives like chat_messages, but the guidance about obtaining the room id is clear and actionable.

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

All mu toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation5/5

Every tool is prefixed with a clear domain (e.g., apps_, blog_, transit_), and the suffix identifies a distinct action or resource. Overlapping tools like archive_search and news_search are explicitly differentiated in their descriptions.

Naming Consistency4/5

All tools consistently use a domain_prefix_suffix pattern, but the suffix is sometimes a verb (create, list, search) and sometimes a noun (inbox, status, address). This minor mixing prevents a perfect score but remains predictable and readable.

Tool Count2/5

With 113 tools, the count is far beyond the typical well-scoped range, even for a broad personal assistant. While each tool is distinct and serves a purpose, the sheer number is overwhelming and could be better organized into separate domain-specific servers.

Completeness4/5

Each domain has near-complete lifecycle coverage, including CRUD and search where relevant, with only minor gaps such as missing apps_delete or events_update. The wide range of covered domains itself demonstrates strong completeness for a general assistant.

Resources