Skip to main content
Glama

manage_workspace

Configure workspace settings, retrieve usage data, and update information for Tally forms management.

Instructions

Manage workspace settings and information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform on workspace
settingsNo

Implementation Reference

  • The main handler logic for the 'manage_workspace' tool in the _handleToolsCall method. It handles the 'get_info' action by calling listWorkspaces on the WorkspaceManagementTool instance and returns the result as text. Other actions return a placeholder message.
    case 'manage_workspace':
      if (args && args.action === 'get_info') {
        const workspaceInfo = await this.tools.workspaceManagement.listWorkspaces();
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(workspaceInfo, null, 2)
            }
          ]
        };
      }
      return {
        content: [
          {
            type: 'text',
            text: 'Workspace management functionality is being implemented'
          }
        ]
      };
  • JSON Schema definition for the 'manage_workspace' tool input, including supported actions: get_info, update_settings, list_members.
      name: 'manage_workspace',
      description: 'Manage workspace settings and information',
      inputSchema: {
        type: 'object',
        properties: {
          action: { 
            type: 'string', 
            enum: ['get_info', 'update_settings', 'list_members'],
            description: 'Action to perform on the workspace'
          },
          settings: {
            type: 'object',
            properties: {
              name: { type: 'string', description: 'Workspace name' },
              description: { type: 'string', description: 'Workspace description' }
            }
          }
        },
        required: ['action']
      }
    },
  • Registration of the generic tool call handler via MCP SDK's setRequestHandler for CallToolRequestSchema, which routes to _handleToolsCall containing the manage_workspace case.
    this.setRequestHandler(CallToolRequestSchema, async (request) => {
      return this._handleToolsCall(request);
    });
  • WorkspaceManagementTool class providing workspace operations, used by the manage_workspace handler. The listWorkspaces method is called for 'get_info' action.
    export class WorkspaceManagementTool {
      private workspaceService: WorkspaceService;
    
      constructor(apiClientConfig: TallyApiClientConfig = {}) {
        this.workspaceService = new WorkspaceService(apiClientConfig);
      }
    
      public async listWorkspaces(options: { page?: number; limit?: number } = {}): Promise<TallyWorkspacesResponse> {
        return this.workspaceService.getWorkspaces(options);
      }
    
      public async getWorkspaceDetails(workspaceId: string): Promise<TallyWorkspace> {
        return this.workspaceService.getWorkspace(workspaceId);
      }
    
      public async inviteUserToWorkspace(workspaceId: string, email: string, role: UserRole): Promise<any> {
        return this.workspaceService.inviteUser(workspaceId, email, role);
      }
    
      public async removeUserFromWorkspace(workspaceId: string, userId: string): Promise<any> {
        return this.workspaceService.removeUser(workspaceId, userId);
      }
    
      public async updateUserRoleInWorkspace(workspaceId: string, userId: string, role: UserRole): Promise<any> {
        return this.workspaceService.updateUserRole(workspaceId, userId, role);
      }
    } 
  • WorkspaceService class that delegates workspace operations to TallyApiClient, used by WorkspaceManagementTool.
    export class WorkspaceService {
      private apiClient: TallyApiClient;
    
      constructor(config: TallyApiClientConfig = {}) {
        this.apiClient = new TallyApiClient(config);
      }
    
      public async getWorkspaces(options: { page?: number; limit?: number } = {}): Promise<TallyWorkspacesResponse> {
        return this.apiClient.getWorkspaces(options);
      }
    
      public async getWorkspace(workspaceId: string): Promise<TallyWorkspace> {
        return this.apiClient.getWorkspace(workspaceId);
      }
    
      public async inviteUser(workspaceId: string, email: string, role: UserRole): Promise<any> {
        return this.apiClient.inviteUserToWorkspace(workspaceId, email, role);
      }
    
      public async removeUser(workspaceId: string, userId: string): Promise<any> {
        return this.apiClient.removeUserFromWorkspace(workspaceId, userId);
      }
    
      public async updateUserRole(workspaceId: string, userId: string, role: UserRole): Promise<any> {
        return this.apiClient.updateUserRole(workspaceId, userId, role);
      }
    } 
Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies mutation ('manage') but doesn't disclose behavioral traits like permissions needed, whether actions are destructive, rate limits, or response formats. The description is too generic to inform the agent about critical operational aspects, such as which actions might modify data versus retrieve it.

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 no wasted words. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration. Every word earns its place, making it easy to parse quickly.

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 tool's complexity (multiple actions, nested parameters) and lack of annotations and output schema, the description is incomplete. It doesn't explain the scope of actions, what 'settings' entails, or behavioral implications. For a tool with potential mutations and varied operations, more context is needed to guide effective use.

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 50%, with the 'action' parameter well-documented via enum and description, but 'settings' parameter lacks schema descriptions. The description adds no meaning beyond the schema; it doesn't explain what 'settings' includes or how actions interact with parameters. Baseline is 3 due to moderate schema coverage, but the description fails to compensate for gaps.

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 'Manage workspace settings and information' states a general purpose but is vague about specific actions. It mentions 'settings and information' but doesn't specify what management entails or differentiate from sibling tools like 'manage_team'. The verb 'manage' is broad and lacks specificity about the actual operations available.

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 for choosing between actions, or how it relates to sibling tools. For example, it doesn't clarify when to use 'manage_workspace' versus 'manage_team' or other workspace-related operations, leaving usage ambiguous.

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/learnwithcc/tally-mcp'

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