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;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'Get' but 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. This leaves significant gaps for a tool that likely interacts with meeting data.

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, efficient sentence with zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary details.

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 meeting chat tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'chat messages' entail (e.g., text, timestamps, senders), how results are structured, or any limitations, making it inadequate for effective use by an AI agent.

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?

Schema description coverage is 100%, with the parameter 'bot_id' clearly documented. The description adds no additional meaning beyond the schema, such as explaining why bot_id is needed or how it relates to chat messages. Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get chat messages from the meeting' states a clear verb ('Get') and resource ('chat messages'), but it's vague about scope and context. It doesn't specify whether this retrieves all messages, recent messages, or filtered messages, nor does it distinguish from sibling tools like 'get_meeting_transcript' or 'send_chat_message'.

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. With siblings like 'get_meeting_transcript' (possibly for spoken content) and 'send_chat_message' (for sending), the description lacks context on prerequisites, timing, or exclusions, leaving usage unclear.

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