Skip to main content
Glama

toggl_list_workspaces

Retrieve all available workspaces from Toggl Track to manage time tracking projects and organize team collaboration.

Instructions

List all available workspaces

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the toggl_list_workspaces tool. Fetches workspaces using TogglAPI and returns formatted JSON list.
    case 'toggl_list_workspaces': {
      const workspaces = await api.getWorkspaces();
      
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({ 
            count: workspaces.length,
            workspaces: workspaces.map(ws => ({
              id: ws.id,
              name: ws.name,
              premium: ws.premium,
              default_currency: ws.default_currency
            }))
          }, null, 2)
        }]
      };
    }
  • Input schema definition for toggl_list_workspaces tool (no parameters required).
    name: 'toggl_list_workspaces',
    description: 'List all available workspaces',
    inputSchema: {
      type: 'object',
      properties: {},
      required: []
    },
  • src/index.ts:386-388 (registration)
    Registration of all tools including toggl_list_workspaces via the ListToolsRequestSchema handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
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. 'List all available workspaces' implies a read-only operation but doesn't disclose behavioral traits like authentication requirements, rate limits, pagination, or whether it returns active/inactive workspaces. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 with zero wasted words. It's appropriately sized for a simple listing tool and front-loads the essential information without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema), the description is adequate but minimal. It states what the tool does but lacks context about authentication, workspace states, or relationship to sibling tools. For a read operation with no annotations, it should ideally mention authentication needs or data freshness, but it meets minimum viability.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter semantics, and it correctly doesn't mention any parameters. Baseline 4 is appropriate for zero-parameter tools where the schema already covers everything.

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 action ('List') and resource ('all available workspaces'), making the purpose immediately understandable. It doesn't specifically differentiate from sibling tools like 'toggl_workspace_summary' which might provide aggregated data versus a raw list, but the verb+resource combination is unambiguous.

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. With sibling tools like 'toggl_workspace_summary' that might offer summarized workspace data, there's no indication of whether this tool is for raw listings, administrative purposes, or initial setup. No prerequisites or exclusions are mentioned.

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/verygoodplugins/mcp-toggl'

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