Skip to main content
Glama

get_room_meeting_details

Retrieve detailed information about a Webex meeting associated with a specific room using the room's unique identifier for streamlined access and management.

Instructions

Get details of a Webex meeting for a specific room.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomIdYesThe unique identifier for the room.

Implementation Reference

  • The core handler function that executes the tool: makes a GET request to Webex API endpoint `/rooms/{roomId}/meetingInfo` to retrieve meeting details, handles errors, and returns the data or error message.
    const executeFunction = async ({ roomId }) => {
    
      try {
        // Construct the URL with the roomId
        const url = getWebexUrl(`/rooms/${encodeURIComponent(roomId)}/meetingInfo`);
    
        // Set up headers for the request
        const headers = getWebexHeaders();
    
        // Perform the fetch request
        const response = await fetch(url, {
          method: 'GET',
          headers
        });
    
        // Check if the response was successful
        if (!response.ok) {
          const errorData = await response.json();
          throw new Error(errorData);
        }
    
        // Parse and return the response data
        const data = await response.json();
        return data;
      } catch (error) {
        console.error('Error fetching room meeting details:', error);
        return { error: 'An error occurred while fetching room meeting details.' };
      }
    };
  • The apiTool object defining the tool's name, description, input schema (roomId: string, required), and reference to the handler function. This object is exported and dynamically loaded for MCP registration.
    const apiTool = {
      function: executeFunction,
      definition: {
        type: 'function',
        function: {
          name: 'get_room_meeting_details',
          description: 'Get details of a Webex meeting for a specific room.',
          parameters: {
            type: 'object',
            properties: {
              roomId: {
                type: 'string',
                description: 'The unique identifier for the room.'
              }
            },
            required: ['roomId']
          }
        }
      }
    };
  • tools/paths.js:19-19 (registration)
    The relative path to the tool's implementation file listed in the toolPaths array, which is used by lib/tools.js discoverTools() to dynamically import and prepare the tool for registration in mcpServer.js.
    'webex-public-workspace/webex-messaging/get-room-meeting-details.js',
  • Generic registration loop in the MCP server that registers all discovered tools (including 'get_room_meeting_details') by name using McpServer.registerTool(), converting JSON schema to Zod inputSchema, and wrapping the tool's function.
    for (const tool of tools) {
      const definition = tool.definition?.function;
      if (!definition) {
        console.error(`[MCP Server] Skipping tool with invalid definition:`, tool);
        continue;
      }
    
      try {
        server.registerTool(
          definition.name,
          {
            title: definition.name.replace(/_/g, ' ').replace(/\b\w/g, l => l.toUpperCase()),
            description: definition.description,
            // MCP SDK v1.17.4 requires inputSchema with Zod schemas for parameter validation
            inputSchema: convertJsonSchemaToZod(definition.parameters?.properties || {}, definition.parameters?.required || [])
          },
          async (args) => {
            try {
              // Debug logging to see what we actually receive
              console.error(`[DEBUG] Tool ${definition.name} called with args:`, JSON.stringify(args));
              console.error(`[DEBUG] Args type:`, typeof args);
              console.error(`[DEBUG] Args keys:`, Object.keys(args || {}));
    
              // Handle both function and handler patterns
              const toolFunction = tool.function || tool.handler;
              if (!toolFunction) {
                throw new Error(`Tool ${definition.name} has no function or handler`);
              }
    
              const result = await toolFunction(args);
              return {
                content: [{
                  type: 'text',
                  text: JSON.stringify(result, null, 2)
                }]
              };
            } catch (error) {
              console.error(`[MCP Server] Tool ${definition.name} error:`, error);
              return {
                content: [{
                  type: 'text',
                  text: `Error: ${error.message}`
                }],
                isError: true
              };
            }
          }
        );
      } catch (error) {
        console.error(`[MCP Server] Failed to register tool ${definition.name}:`, error);
      }
    }
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 this is a read operation ('Get details'), implying it's likely non-destructive, but doesn't mention authentication requirements, rate limits, error handling, or what details are returned (e.g., meeting ID, participants, time). For a tool with no 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, clear sentence that directly states the tool's purpose without any fluff or redundancy. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly and efficiently.

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 details tool with no annotations and no output schema, the description is insufficient. It doesn't explain what details are returned (e.g., structured data like meeting time, attendees), potential errors, or how it differs from similar tools. This leaves the agent with incomplete 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 'roomId' clearly documented as 'The unique identifier for the room.' The description adds no additional meaning beyond this, such as format examples or constraints. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema does the heavy lifting for parameter semantics.

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 details') and resource ('Webex meeting for a specific room'), making the purpose understandable. However, it doesn't distinguish this tool from similar siblings like 'get_room_details' or 'get_event_details', which could also involve meeting-related information, leaving some ambiguity about its specific scope.

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_room_details' and 'get_event_details' that might overlap in functionality, there's no indication of prerequisites, constraints, or specific scenarios where this tool is preferred, leaving the agent to guess based on the name alone.

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

Related 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/Kashyap-AI-ML-Solutions/webex-messaging-mcp-server'

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