Skip to main content
Glama
Angad-2002

Attendee MCP Server

by Angad-2002

send_chat_message

Send chat messages from AI meeting bots to participants during video conferences on platforms like Zoom, Google Meet, and Microsoft Teams.

Instructions

Send a chat message from the bot to the meeting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bot_idYesID of the bot that should send the message
messageYesMessage text to send

Implementation Reference

  • The primary handler function for the 'send_chat_message' tool. Validates bot_id and message inputs, makes a POST API request to send the message via the backend, and returns a formatted success confirmation.
    private async sendChatMessage(args: Record<string, unknown>) {
      const bot_id = args.bot_id as string;
      const message = args.message as string;
      
      if (!bot_id || typeof bot_id !== 'string') {
        throw new Error("Missing or invalid required parameter: bot_id");
      }
      
      if (!message || typeof message !== 'string') {
        throw new Error("Missing or invalid required parameter: message");
      }
      
      await this.makeApiRequest(`/api/v1/bots/${bot_id}/send_chat_message`, "POST", {
        message
      });
    
      return {
        content: [
          {
            type: "text",
            text: `✅ Chat message sent from bot ${bot_id}: "${message}"`,
          },
        ],
      };
    }
  • Tool definition including name, description, and input schema specifying required 'bot_id' (string) and 'message' (string) parameters.
    {
      name: "send_chat_message",
      description: "Send a chat message from the bot to the meeting",
      inputSchema: {
        type: "object",
        properties: {
          bot_id: {
            type: "string",
            description: "ID of the bot that should send the message",
          },
          message: {
            type: "string",
            description: "Message text to send",
          },
        },
        required: ["bot_id", "message"],
      },
    },
  • src/index.ts:425-426 (registration)
    Registration and dispatch of the 'send_chat_message' tool handler within the CallToolRequestSchema switch statement.
    case "send_chat_message":
      return await this.sendChatMessage(args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it implies a write operation ('send'), it doesn't address critical aspects like required permissions, whether the message is broadcast or targeted, rate limits, or error conditions. This leaves significant gaps in understanding how the tool behaves.

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, direct sentence that efficiently conveys the core action without any unnecessary words. It's front-loaded with the essential information, making it easy to parse and understand immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a chat-sending operation with no annotations or output schema, the description is incomplete. It lacks details on behavioral traits (e.g., permissions, side effects), response format, or error handling, which are crucial for an agent to use this tool effectively in a meeting context.

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 has 100% description coverage, clearly documenting both required parameters (bot_id and message). The description doesn't add any additional semantic context beyond what the schema provides, such as format examples or constraints, so it meets the baseline for high schema coverage.

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 clearly states the action ('send') and resource ('a chat message from the bot to the meeting'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'make_bot_speak' or 'send_image_to_meeting', which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'make_bot_speak' or 'send_image_to_meeting'. It also doesn't mention prerequisites such as needing an active meeting or bot setup, leaving the agent with insufficient context for proper tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Angad-2002/attendee-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server