Skip to main content
Glama
Angad-2002

Attendee MCP Server

by Angad-2002

get_chat_messages

Retrieve chat messages from meetings for a specific bot to monitor conversations and extract key discussion points.

Instructions

Get chat messages from the meeting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bot_idYesID of the bot to get chat messages for

Implementation Reference

  • The main handler function for the 'get_chat_messages' tool. It validates the bot_id parameter, makes an API request to retrieve chat messages, formats the response using formatChatMessages helper, and returns it as MCP content.
    private async getChatMessages(args: Record<string, unknown>) {
      const bot_id = args.bot_id as string;
      
      if (!bot_id || typeof bot_id !== 'string') {
        throw new Error("Missing or invalid required parameter: bot_id");
      }
      
      const data = await this.makeApiRequest(`/api/v1/bots/${bot_id}/chat_messages`);
    
      return {
        content: [
          {
            type: "text",
            text: this.formatChatMessages(data, bot_id),
          },
        ],
      };
    }
  • src/index.ts:321-334 (registration)
    Registration of the 'get_chat_messages' tool in the list of tools provided by ListToolsRequestSchema, including name, description, and input schema.
    {
      name: "get_chat_messages",
      description: "Get chat messages from the meeting",
      inputSchema: {
        type: "object",
        properties: {
          bot_id: {
            type: "string",
            description: "ID of the bot to get chat messages for",
          },
        },
        required: ["bot_id"],
      },
    },
  • src/index.ts:428-429 (registration)
    Dispatcher case in the CallToolRequestSchema handler that routes calls to the getChatMessages method.
    case "get_chat_messages":
      return await this.getChatMessages(args);
  • Helper function that formats the raw chat messages data into a human-readable string with timestamps and sender names.
    private formatChatMessages(data: any, botId: string): string {
      if (!Array.isArray(data) || data.length === 0) {
        return `šŸ’¬ No chat messages found for bot ${botId}`;
      }
    
      let chatOutput = `šŸ’¬ Chat Messages for bot ${botId}:\n\n`;
      chatOutput += "─".repeat(50) + "\n";
      
      data.forEach((message: any) => {
        const timestamp = new Date(message.created_at).toLocaleTimeString();
        chatOutput += `[${timestamp}] ${message.sender_name}:\n${message.message}\n\n`;
      });
      
      chatOutput += "─".repeat(50) + `\nšŸ“Š Total messages: ${data.length}`;
      return chatOutput;
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
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 but only states the basic action. It doesn't disclose behavioral traits such as whether this is a read-only operation, if it requires specific permissions, how messages are returned (e.g., format, pagination), or any rate limits, leaving significant gaps in understanding.

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 with no wasted words, making it highly concise and front-loaded. It efficiently communicates the core purpose without unnecessary elaboration.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., message list format, timestamps), behavioral constraints, or how it integrates with sibling tools, making it inadequate for a tool that likely involves data retrieval.

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 description coverage is 100%, with the single parameter 'bot_id' well-documented in the schema. The description adds no additional meaning beyond implying the bot is associated with the meeting, so it meets the baseline for high schema coverage without extra value.

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 verb 'Get' and the resource 'chat messages from the meeting', making the purpose understandable. It doesn't explicitly differentiate from siblings like 'get_meeting_transcript' or 'send_chat_message', but the core action is well-defined.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't specify if this retrieves all messages, recent ones, or how it differs from 'get_meeting_transcript' or other chat-related tools, leaving the agent without context for selection.

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