Skip to main content
Glama

get_bot_status

Check the current operational status of a meeting bot to verify its availability and activity during video calls.

Instructions

Get the current status of a meeting bot

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bot_idYesID of the bot to check

Implementation Reference

  • The core handler function for the 'get_bot_status' tool. Validates the bot_id parameter, makes an API request to retrieve the bot status, formats the response using formatBotStatus, and returns it as MCP content.
    private async getBotStatus(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}`);
    
      return {
        content: [
          {
            type: "text",
            text: this.formatBotStatus(data),
          },
        ],
      };
    }
  • src/index.ts:225-237 (registration)
    Registers the 'get_bot_status' tool in the ListToolsRequestSchema handler, providing name, description, and input schema.
      name: "get_bot_status",
      description: "Get the current status of a meeting bot",
      inputSchema: {
        type: "object",
        properties: {
          bot_id: {
            type: "string",
            description: "ID of the bot to check",
          },
        },
        required: ["bot_id"],
      },
    },
  • src/index.ts:401-402 (registration)
    In the CallToolRequestSchema switch dispatcher, routes calls to the getBotStatus handler method.
    case "get_bot_status":
      return await this.getBotStatus(args);
  • Input schema definition for the 'get_bot_status' tool, specifying required 'bot_id' parameter.
    inputSchema: {
      type: "object",
      properties: {
        bot_id: {
          type: "string",
          description: "ID of the bot to check",
        },
      },
      required: ["bot_id"],
    },
  • Helper function used by the handler to format the raw API response into a readable markdown string with status icons.
    private formatBotStatus(data: any): string {
      const stateIcon = (data.state === 'joining' || data.state === 'joined' || data.state === 'joined_recording') ? "✅" : "❌";
      const transcriptIcon = data.transcription_state === 'complete' ? "✅" : "⏳";
    
      return [
        `🤖 Bot Status for ${data.id}:`,
        "",
        `📊 State: ${data.state} ${stateIcon}`,
        `📝 Transcription State: ${data.transcription_state} ${transcriptIcon}`,
        `🔗 Meeting URL: ${data.meeting_url}`,
        "",
        `${stateIcon} Bot is ${(data.state === 'joining' || data.state === 'joined' || data.state === 'joined_recording') ? "active and recording" : "not active"}`,
        `${transcriptIcon} Transcript is ${data.transcription_state === 'complete' ? "ready" : "not ready yet"}`,
      ].join("\n");
    }
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 it 'Get[s] the current status' but doesn't specify what 'status' entails (e.g., online/offline, active/inactive, error states), whether it's a read-only operation, any rate limits, or authentication needs. This leaves significant gaps for a tool with no annotation coverage.

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 front-loaded with the core action and resource, making it easy to parse quickly 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 no annotations and no output schema, the description is incomplete for a tool that retrieves status information. It doesn't explain what 'status' means, potential return values, or behavioral traits like safety or performance. For a read operation with undefined output, this lacks necessary 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?

Schema description coverage is 100%, with the parameter 'bot_id' clearly documented in the schema as 'ID of the bot to check'. The description adds no additional meaning beyond this, such as format examples or context about bot IDs. 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.

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 'current status of a meeting bot', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_chat_messages' or 'get_meeting_transcript' that also retrieve information about bots/meetings, so it misses full sibling distinction.

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. With siblings like 'get_chat_messages' and 'get_meeting_transcript' that might retrieve related data, there's no indication of context, prerequisites, or exclusions for choosing this specific status-checking tool.

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/rexposadas/attendee-mcp'

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