Skip to main content
Glama

get_person_details

Retrieve detailed information about a person, including optional Webex Calling user data, by providing their unique ID via the Webex Messaging API.

Instructions

Get details of a person by their ID from Webex Messaging API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
callingDataNoInclude Webex Calling user details in the response.
personIdYesThe unique identifier for the person.

Implementation Reference

  • The core handler function that makes an HTTP GET request to the Webex API endpoint `/people/{personId}` to retrieve person details, including optional calling data.
    const executeFunction = async ({ personId, callingData = true }) => {
    
      try {
        // Construct the URL with the personId and query parameters
        const url = new URL(getWebexUrl(`/people/${encodeURIComponent(personId)}`));
        url.searchParams.append('callingData', callingData);
    
        // Set up headers for the request
        const headers = getWebexHeaders();
    
        // Perform the fetch request
        const response = await fetch(url.toString(), {
          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 person details:', error);
        return { error: 'An error occurred while fetching person details.' };
      }
    };
  • The JSON schema definition for the tool, specifying input parameters (personId required, callingData optional) used for validation.
    definition: {
      type: 'function',
      function: {
        name: 'get_person_details',
        description: 'Get details of a person by their ID from Webex Messaging API.',
        parameters: {
          type: 'object',
          properties: {
            personId: {
              type: 'string',
              description: 'The unique identifier for the person.'
            },
            callingData: {
              type: 'boolean',
              description: 'Include Webex Calling user details in the response.'
            }
          },
          required: ['personId']
        }
      }
    }
  • tools/paths.js:29-29 (registration)
    The tool file path is included in the toolPaths array, enabling dynamic discovery and loading of the tool.
    'webex-public-workspace/webex-messaging/get-person-details.js',
  • lib/tools.js:7-16 (registration)
    The discoverTools function dynamically imports all tool files from toolPaths (including get-person-details.js) and extracts the apiTool object for registration.
    export async function discoverTools() {
      const toolPromises = toolPaths.map(async (file) => {
        const module = await import(`../tools/${file}`);
        return {
          ...module.apiTool,
          path: file,
        };
      });
      return Promise.all(toolPromises);
    }
  • mcpServer.js:86-138 (registration)
    The MCP server loop that registers each discovered tool (including get_person_details) using server.registerTool, converting schema to Zod and wrapping the handler.
    // Register each tool individually (NO inputSchema in registerTool call)
    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?

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a 'Get' operation, implying read-only behavior, but doesn't mention authentication requirements, rate limits, error conditions, or what details are included in the response. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 gets straight to the point with no wasted words. It's appropriately sized for a simple retrieval tool and front-loads the core purpose immediately.

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?

For a retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'details' are returned, doesn't mention authentication or error handling, and provides no context about the Webex Messaging API integration. With rich sibling tools available, more completeness is needed to help an agent use this 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%, so the schema already documents both parameters thoroughly. The description doesn't add any meaning beyond what's in the schema - it mentions getting details by ID but doesn't explain parameter interactions or provide additional context about the 'callingData' flag. This meets the baseline for high schema coverage.

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 details') and resource ('a person by their ID from Webex Messaging API'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_my_own_details' or 'list_people', which could cause confusion about when to use this specific retrieval method versus alternatives.

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 like 'get_my_own_details' (for self-details) or 'list_people' (for multiple people). It also doesn't mention prerequisites such as needing a valid person ID or when this tool is appropriate compared to other get_* tools in the sibling list.

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