Skip to main content
Glama
TykanN

Swit MCP Server

by TykanN

swit-workspace-list

Get a paginated list of workspaces from Swit, filterable by name, to view and manage your collaboration spaces.

Instructions

Retrieve list of workspaces

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNo
limitNo
nameNo

Implementation Reference

  • The handler function for 'swit-workspace-list'. Validates args via WorkspaceListArgsSchema and delegates to SwitClient.listWorkspaces().
    export const handleWorkspaceList = async (switClient: SwitClient, args: any) => {
      const validatedArgs = WorkspaceListArgsSchema.parse(args);
      return await switClient.listWorkspaces(validatedArgs);
    };
  • Input schema (Zod) for workspace list arguments, accepting optional offset, limit, and name fields.
    export const WorkspaceListArgsSchema = z.object({
      offset: z.string().optional(),
      limit: z.number().min(1).max(100).optional(),
      name: z.string().optional(),
    });
  • Tool registration with name 'swit-workspace-list', description, and inputSchema derived from WorkspaceListArgsSchema.
    {
      name: 'swit-workspace-list',
      description: 'Retrieve list of workspaces',
      inputSchema: zodToJsonSchema(WorkspaceListArgsSchema),
    },
  • Handler mapping: maps tool name 'swit-workspace-list' to handleWorkspaceList function, merged into toolHandlers in index.ts on line 109.
    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),
    });
  • SwitClient.listWorkspaces() — makes the actual HTTP GET request to /api/workspace.list with the validated args.
    async listWorkspaces(args: WorkspaceListArgs): Promise<WorkspaceListResponse> {
      const response = await this.client.get('/api/workspace.list', { params: args });
      return response.data;
    }
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, pagination, sorting, or error handling. The agent has no insight into side effects or limitations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only one sentence, but it is too sparse to be informative. While brief, it fails to provide enough detail to guide proper tool usage.

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 absence of annotations and output schema, plus three unexplained parameters, the description is incomplete. It does not cover pagination, filtering, or the structure of the returned data.

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

Parameters1/5

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

The schema has 0% description coverage, and the tool description does not explain any of the three parameters (offset, limit, name). The agent cannot infer their meaning or usage.

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 states 'Retrieve list of workspaces', clearly indicating the resource (workspaces) and action (retrieve list). However, it does not distinguish from sibling tools like swit-channel-list or swit-project-list, which follow the same pattern.

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 (e.g., swit-channel-list). There is no mention of prerequisites, filtering, or context.

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