Skip to main content
Glama
TykanN

Swit MCP Server

by TykanN

swit-workspace-list

Retrieve and manage Swit workspaces to organize team collaboration projects and access workspace data for integration purposes.

Instructions

Retrieve list of workspaces

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNo
limitNo
nameNo

Implementation Reference

  • The handler function that executes the swit-workspace-list tool logic: validates input args and calls switClient.listWorkspaces.
    export const handleWorkspaceList = async (switClient: SwitClient, args: any) => {
      const validatedArgs = WorkspaceListArgsSchema.parse(args);
      return await switClient.listWorkspaces(validatedArgs);
    };
  • Zod schema for input validation of swit-workspace-list tool arguments.
    export const WorkspaceListArgsSchema = z.object({
      offset: z.string().optional(),
      limit: z.number().min(1).max(100).optional(),
      name: z.string().optional(),
    });
  • Tool registration in coreTools array, defining name, description, and input schema for ListTools request.
    {
      name: 'swit-workspace-list',
      description: 'Retrieve list of workspaces',
      inputSchema: zodToJsonSchema(WorkspaceListArgsSchema),
    },
  • Handler factory function that registers the mapping from tool name 'swit-workspace-list' to its handler.
    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 operation. It doesn't disclose whether this is a read-only operation (implied by 'retrieve'), authentication requirements, rate limits, pagination behavior (though parameters suggest it), or what the return format looks like. For a tool with 3 parameters and no output schema, this leaves significant behavioral gaps.

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 just 3 words, front-loaded with the core purpose. There's zero wasted language or redundancy. While it may be too brief for completeness, it earns full marks for conciseness as every word contributes directly to stating the tool's 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 3 undocumented parameters, no annotations, no output schema, and sibling tools that retrieve similar resource types, the description is incomplete. It doesn't help the agent understand what the tool returns, how to use the parameters, or how this differs from other list tools. The minimal description leaves too many contextual gaps 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 provides no parameter information. The 3 parameters (offset, limit, name) are completely undocumented in both schema and description. The description doesn't explain what these parameters do, their purpose, or how they affect the retrieval. This fails to add value beyond the bare schema.

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 workspaces' clearly states the action (retrieve) and resource (workspaces), but it's vague about scope and doesn't distinguish from sibling tools like 'swit-project-list' or 'swit-channel-list' which retrieve different resource types. It meets the basic requirement but lacks specificity about what kind of workspaces or what information is included.

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 about when to use this tool versus alternatives. The description doesn't mention any prerequisites, context for usage, or comparisons to sibling tools like 'swit-project-list' (which might retrieve projects within workspaces). The agent receives no help in selecting this tool appropriately.

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