Skip to main content
Glama
TykanN

Swit MCP Server

by TykanN

swit-channel-list

Retrieve channel lists from Swit workspaces to organize team communication. Filter by type, activity, disclosure, or name to find specific channels.

Instructions

Retrieve list of channels

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspace_idYes
offsetNo
limitNo
typeNo
activityNo
disclosureNo
nameNo

Implementation Reference

  • Main handler function for the 'swit-channel-list' MCP tool. Validates input arguments and calls SwitClient.listChannels.
    export const handleChannelList = async (switClient: SwitClient, args: any) => {
      const validatedArgs = ChannelListArgsSchema.parse(args);
      return await switClient.listChannels(validatedArgs);
    };
  • SwitClient method that performs the actual API call to list channels via axios GET /api/channel.list.
    async listChannels(args: ChannelListArgs): Promise<ChannelListResponse> {
      const response = await this.client.get('/api/channel.list', { params: args });
      return response.data;
    }
  • Zod schema defining the input arguments for listing channels (workspace_id required, pagination and filters optional).
    export const ChannelListArgsSchema = z.object({
      workspace_id: z.string(),
      offset: z.string().optional(),
      limit: z.number().min(1).max(100).optional(),
      type: z.string().optional(),
      activity: z.string().optional(),
      disclosure: z.string().optional(),
      name: z.string().optional(),
    });
  • MCP tool metadata: name, description, and input schema (JSON schema from Zod).
    {
      name: 'swit-channel-list',
      description: 'Retrieve list of channels',
      inputSchema: zodToJsonSchema(ChannelListArgsSchema),
    },
  • Factory registering 'swit-channel-list' handler among core handlers, used by main server.
    export const coreHandlers = (switClient: SwitClient) => ({
      'swit-workspace-list': (args: any) => handleWorkspaceList(switClient, args),
      'swit-channel-list': (args: any) => handleChannelList(switClient, args),
      'swit-message-create': (args: any) => handleMessageCreate(switClient, args),
      'swit-message-comment-create': (args: any) => handleMessageCommentCreate(switClient, args),
      'swit-message-comment-list': (args: any) => handleMessageCommentList(switClient, args),
      'swit-project-list': (args: any) => handleProjectList(switClient, args),
    });
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits like pagination (implied by offset/limit), authentication needs, rate limits, or what 'retrieve' entails (e.g., read-only, potential side effects). This is inadequate for a tool with 7 parameters and no output schema.

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 extremely concise at three words, with no wasted language. It's front-loaded with the core action, though this brevity comes at the cost of completeness.

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 (7 parameters, 1 required, no output schema, no annotations), the description is incomplete. It doesn't address parameter meanings, return values, or usage context, making it insufficient for effective tool selection and invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but adds no parameter information. It doesn't explain what parameters like 'type', 'activity', 'disclosure', or 'name' do, leaving all 7 parameters undocumented beyond their schema types. This fails to provide meaningful context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Retrieve list of channels' clearly states the action (retrieve) and resource (channels), but it's vague about scope or filtering capabilities. It doesn't differentiate from sibling tools like 'swit-workspace-list' or 'swit-project-list' in terms of what type of list this returns.

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. The description doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name and parameters 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

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/TykanN/swit-mcp'

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