Skip to main content
Glama
Angad-2002

Attendee MCP Server

by Angad-2002

get_bot_status

Check the current operational status of a meeting bot to verify its availability and functionality during online meetings.

Instructions

Get the current status of a meeting bot

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bot_idYesID of the bot to check

Implementation Reference

  • The handler function for the 'get_bot_status' tool. It validates the bot_id input, makes an API request to fetch 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),
          },
        ],
      };
    }
  • Input schema definition for the 'get_bot_status' tool, specifying the required 'bot_id' parameter.
    inputSchema: {
      type: "object",
      properties: {
        bot_id: {
          type: "string",
          description: "ID of the bot to check",
        },
      },
      required: ["bot_id"],
    },
  • src/index.ts:225-237 (registration)
    Registration of the 'get_bot_status' tool in the listTools response, including 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"],
      },
    },
  • Helper function used by the handler to format the bot status data into a user-friendly string with icons and status indicators.
    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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves status but doesn't clarify what 'status' entails (e.g., online/offline, active/inactive, error states), whether it's a read-only operation, or if there are rate limits or authentication needs. This leaves significant gaps in understanding the tool's behavior.

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, clear sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and efficient, making it easy to understand at a glance, which aligns well with best practices for conciseness.

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 for a tool that likely returns complex status information. It doesn't explain what the status includes (e.g., operational state, last activity), potential error cases, or how to interpret results, leaving the agent with insufficient context for effective use.

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, with 'bot_id' clearly documented as 'ID of the bot to check'. The description doesn't add any extra meaning beyond this, such as format examples or where to obtain the ID. Given the high schema coverage, a baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 ('Get') and resource ('current status of a meeting bot'), making the purpose evident. However, it doesn't differentiate from potential siblings like 'list_meeting_bots' or 'get_meeting_transcript', which might also provide status-related information, preventing 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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't specify if this is for real-time status checks versus historical data from other tools, or mention prerequisites like needing a bot ID from 'list_meeting_bots'. The description lacks any context for usage decisions.

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