Skip to main content
Glama

get_team_details

Retrieve detailed information for a specific team using its unique identifier within the Webex MCP Server, enabling access to team descriptions and essential data.

Instructions

Get details for a team by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNoThe team's description.
teamIdYesThe unique identifier for the team.

Implementation Reference

  • The handler function `executeFunction` that fetches team details from the Webex API using the provided teamId and optional description parameter.
    const executeFunction = async ({ teamId, description }) => {
    
      try {
        // Construct the URL with the team ID and query parameters
        const url = new URL(getWebexUrl(`/teams/${encodeURIComponent(teamId)}`));
        if (description) {
          url.searchParams.append('description', description);
        }
    
        // 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(JSON.stringify(errorData));
        }
    
        // Parse and return the response data
        const data = await response.json();
        return data;
      } catch (error) {
        console.error('Error getting team details:', error);
        return { error: 'An error occurred while getting team details.' };
      }
    };
  • JSON schema defining the input parameters for the get_team_details tool: required 'teamId' (string) and optional 'description' (string).
      function: {
        name: 'get_team_details',
        description: 'Get details for a team by ID.',
        parameters: {
          type: 'object',
          properties: {
            teamId: {
              type: 'string',
              description: 'The unique identifier for the team.'
            },
            description: {
              type: 'string',
              description: 'The team\'s description.'
            }
          },
          required: ['teamId']
        }
      }
    }
  • The `apiTool` object that bundles the handler function and schema definition, exported for registration in the MCP tools system.
    const apiTool = {
      function: executeFunction,
      definition: {
        type: 'function',
        function: {
          name: 'get_team_details',
          description: 'Get details for a team by ID.',
          parameters: {
            type: 'object',
            properties: {
              teamId: {
                type: 'string',
                description: 'The unique identifier for the team.'
              },
              description: {
                type: 'string',
                description: 'The team\'s description.'
              }
            },
            required: ['teamId']
          }
        }
      }
    };
  • tools/paths.js:32-32 (registration)
    Lists the relative path to the get-team-details tool file in the central toolPaths array, likely used to dynamically load and register tools.
    'webex-public-workspace/webex-messaging/get-team-details.js',
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 it's a read operation ('Get'), implying it's likely safe and non-destructive, but doesn't cover aspects like authentication needs, rate limits, error conditions, or what details are returned (e.g., team name, members, settings). This leaves significant gaps for a tool with no annotation support.

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 directly states the tool's purpose without unnecessary words or fluff, making it easy to parse and front-loaded.

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 read tool. It doesn't explain what details are returned (e.g., structured data like team attributes), potential errors, or how it differs from similar tools, leaving the agent with insufficient context to use it effectively beyond basic parameter input.

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 fully documents both parameters (teamId and description). The description adds no additional meaning beyond implying 'teamId' is required, which is already clear from the schema. This meets the baseline of 3 when 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 resource ('details for a team by ID'), making the purpose specific and understandable. However, it doesn't differentiate from sibling tools like 'list_teams' or 'get_team_membership_details', which would require explicit comparison to score a 5.

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 mention using 'list_teams' for multiple teams or 'get_team_membership_details' for membership info, leaving the agent to infer usage from context 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