Skip to main content
Glama
Angad-2002

Attendee MCP Server

by Angad-2002

send_image_to_meeting

Display images in Google Meet meetings using a bot. Send image URLs to share visual content during video conferences.

Instructions

Send an image to the meeting through the bot (Google Meet only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bot_idYesID of the bot that should display the image
image_urlYesHTTPS URL of the image to display

Implementation Reference

  • The handler function that executes the tool logic: validates bot_id and image_url, calls the API to send the image, and returns a success message.
    private async sendImageToMeeting(args: Record<string, unknown>) {
      const bot_id = args.bot_id as string;
      const image_url = args.image_url as string;
      
      if (!bot_id || typeof bot_id !== 'string') {
        throw new Error("Missing or invalid required parameter: bot_id");
      }
      
      if (!image_url || typeof image_url !== 'string') {
        throw new Error("Missing or invalid required parameter: image_url");
      }
    
      if (!image_url.startsWith('https://')) {
        throw new Error("Image URL must start with https://");
      }
      
      await this.makeApiRequest(`/api/v1/bots/${bot_id}/output_image`, "POST", {
        url: image_url
      });
    
      return {
        content: [
          {
            type: "text",
            text: `āœ… Image sent to meeting from bot ${bot_id}\nšŸ“· Image URL: ${image_url}\n\nšŸ’” The image should now be displayed in the meeting (Google Meet only)!`,
          },
        ],
      };
    }
  • Input schema defining parameters bot_id and image_url for the tool.
    inputSchema: {
      type: "object",
      properties: {
        bot_id: {
          type: "string",
          description: "ID of the bot that should display the image",
        },
        image_url: {
          type: "string",
          description: "HTTPS URL of the image to display",
        },
      },
      required: ["bot_id", "image_url"],
    },
  • src/index.ts:349-366 (registration)
    Tool registration in the listTools response, defining name, description, and input schema.
    {
      name: "send_image_to_meeting",
      description: "Send an image to the meeting through the bot (Google Meet only)",
      inputSchema: {
        type: "object",
        properties: {
          bot_id: {
            type: "string",
            description: "ID of the bot that should display the image",
          },
          image_url: {
            type: "string",
            description: "HTTPS URL of the image to display",
          },
        },
        required: ["bot_id", "image_url"],
      },
    },
  • src/index.ts:434-435 (registration)
    Switch case in CallToolRequest handler that dispatches to the sendImageToMeeting method.
    case "send_image_to_meeting":
      return await this.sendImageToMeeting(args);
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 mentions the action 'Send an image' and platform 'Google Meet only', but fails to describe critical behaviors such as required permissions, whether this is a read/write operation, potential rate limits, error conditions, or what happens if the bot isn't available. This leaves significant gaps for a tool that likely involves mutation and external dependencies.

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 that front-loads the core purpose without unnecessary words. Every part ('Send an image to the meeting through the bot (Google Meet only)') contributes directly to understanding the tool's function, making it highly concise and well-structured.

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 sending media in a live meeting context, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., success/failure responses, timing constraints), does not explain return values or errors, and fails to address dependencies like bot availability. For a mutation tool with external interactions, this leaves too much unspecified.

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 both parameters ('bot_id' and 'image_url') clearly documented in the schema. The description adds no additional parameter semantics beyond implying the image is sent via a bot in Google Meet, which is already inferred from the tool name and schema. This meets the baseline for high schema coverage but doesn't enhance understanding.

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 ('Send an image') and target ('to the meeting through the bot'), with the specific platform constraint 'Google Meet only' adding useful specificity. However, it doesn't explicitly distinguish this tool from sibling tools like 'send_video_to_meeting' or 'send_chat_message' beyond the media type, missing full sibling differentiation.

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 minimal guidance, only implying usage for sending images in Google Meet meetings via a bot. It offers no explicit when-to-use advice, no prerequisites (e.g., bot must be active), and no alternatives (e.g., using 'send_chat_message' for text instead), leaving the agent to infer context from the tool name and limited description.

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