Skip to main content
Glama

get_team_info

Retrieve workspace details from Slack, including team information and configuration, to understand the current workspace environment.

Instructions

Get information about the Slack workspace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_team_info' tool. It validates input with getTeamInfoSchema, then calls Slack's team.info() API via the client wrapper and returns the team information.
    export async function getTeamInfo(client: SlackClientWrapper, args: unknown) {
      getTeamInfoSchema.parse(args ?? {});
    
      return await client.safeCall(async () => {
        const result = await client.getClient().team.info();
    
        return {
          team: result.team,
        };
      });
    }
  • Zod schema definition for validating inputs to the getTeamInfo tool. It defines an empty object schema, indicating no input parameters are required.
    export const getTeamInfoSchema = z.object({});
  • src/index.ts:397-404 (registration)
    Registers the 'get_team_info' tool in the MCP server's tools list, providing name, description, and input schema for the list_tools request.
    {
      name: 'get_team_info',
      description: 'Get information about the Slack workspace',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/index.ts:441-441 (registration)
    Maps incoming 'get_team_info' tool calls to the workspaceTools.getTeamInfo handler function in the toolHandlers object used by the call_tool request handler.
    get_team_info: (args) => workspaceTools.getTeamInfo(slackClient, args),
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 only states the action ('Get information') without detailing what information is returned, whether it requires specific permissions, or any rate limits or constraints. This leaves significant gaps for a tool with no annotation coverage.

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 directly states the tool's purpose without any unnecessary words or fluff. It is front-loaded and appropriately sized for its simple function.

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. It doesn't explain what information is returned (e.g., workspace name, ID, settings) or any behavioral aspects like permissions or data format. For a tool with no structured data to supplement it, this leaves too many unknowns for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description doesn't mention any parameters, which is appropriate since there are none, so it doesn't need to compensate for gaps. A baseline of 4 is applied as it correctly aligns with the parameter-less design.

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 ('information about the Slack workspace'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like get_channel_info or get_user_info, which target specific resources rather than the entire workspace, so it doesn't fully distinguish from 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_channel_info or get_user_info, nor does it mention any prerequisites or exclusions. It simply states what the tool does without contextual usage information.

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/Hais/slack-bot-mcp'

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