Skip to main content
Glama
Angad-2002

Attendee MCP Server

by Angad-2002

remove_meeting_bot

Remove an AI bot from a meeting by specifying its ID to manage automated participants in platforms like Zoom, Google Meet, or Microsoft Teams.

Instructions

Remove a bot from a meeting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bot_idYesID of the bot to remove

Implementation Reference

  • The handler function that validates the bot_id, makes a POST request to the API to make the bot leave the meeting, and returns a formatted response with success message and updated bot status.
    private async removeMeetingBot(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}/leave`, "POST", {});
    
      return {
        content: [
          {
            type: "text",
            text: `✅ Successfully requested bot ${bot_id} to leave the meeting.\n\n📊 Updated Status:\n${this.formatBotStatus(data)}`,
          },
        ],
      };
    }
  • Input schema defining the required 'bot_id' parameter as a string.
    inputSchema: {
      type: "object",
      properties: {
        bot_id: {
          type: "string",
          description: "ID of the bot to remove",
        },
      },
      required: ["bot_id"],
    },
  • src/index.ts:261-274 (registration)
    Tool registration in the listTools handler, specifying name, description, and input schema.
    {
      name: "remove_meeting_bot",
      description: "Remove a bot from a meeting",
      inputSchema: {
        type: "object",
        properties: {
          bot_id: {
            type: "string",
            description: "ID of the bot to remove",
          },
        },
        required: ["bot_id"],
      },
    },
  • src/index.ts:419-420 (registration)
    Dispatch case in the CallToolRequestSchema handler that routes to the removeMeetingBot function.
    case "remove_meeting_bot":
      return await this.removeMeetingBot(args);
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 of behavioral disclosure. It states the action is 'Remove,' implying a mutation, but doesn't describe effects (e.g., whether the bot can be re-added, if it's permanent, or if it requires specific permissions). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 zero waste—'Remove a bot from a meeting'—front-loading the core action and resource. It's appropriately sized for a simple tool, making it easy to parse 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 tool's complexity (a mutation with no annotations and no output schema), the description is incomplete. It lacks information on behavioral traits (e.g., reversibility, permissions), usage context, or what happens post-removal. For a tool that modifies state, this leaves critical gaps for an agent to operate safely and effectively.

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' fully documented in the schema as 'ID of the bot to remove.' The description adds no additional meaning beyond this, such as format examples or where to find the ID. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 ('Remove') and the resource ('a bot from a meeting'), making the purpose immediately understandable. It distinguishes from siblings like 'delete_bot_data' (which might delete data rather than remove from a meeting) and 'list_meeting_bots' (which is a read operation). However, it doesn't specify if this is a permanent removal or just disconnection, which slightly limits specificity.

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. It doesn't mention prerequisites (e.g., bot must be in the meeting), exclusions (e.g., cannot remove if meeting is ended), or comparisons to siblings like 'delete_bot_data' (which might delete bot data entirely). This leaves the agent guessing about appropriate contexts.

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