Skip to main content
Glama

asana_list_workspaces

Retrieve all available Asana workspaces to organize projects and tasks across teams. Use optional fields to customize the data returned.

Instructions

List all available workspaces in Asana

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opt_fieldsNoComma-separated list of optional fields to include

Implementation Reference

  • Executes the 'asana_list_workspaces' tool by calling the AsanaClientWrapper's listWorkspaces method with the provided arguments and returns the JSON-stringified response.
    case "asana_list_workspaces": {
      const response = await asanaClient.listWorkspaces(args);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Defines the Tool object with name, description, and input schema allowing optional 'opt_fields' parameter.
    export const listWorkspacesTool: Tool = {
      name: "asana_list_workspaces",
      description: "List all available workspaces in Asana",
      inputSchema: {
        type: "object",
        properties: {
          opt_fields: {
            type: "string",
            description: "Comma-separated list of optional fields to include"
          }
        }
      }
    };
  • Core implementation that calls the Asana SDK's WorkspacesApi.getWorkspaces(opts) and returns the data.
    async listWorkspaces(opts: any = {}) {
      const response = await this.workspaces.getWorkspaces(opts);
      return response.data;
    }
  • Includes the listWorkspacesTool in the all_tools array for tool registration.
    listWorkspacesTool,
  • Imports the tool definition for registration.
    import { listWorkspacesTool } from './tools/workspace-tools.js';
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it's a list operation but doesn't mention whether it requires authentication, has rate limits, returns paginated results, or what format the output takes. For a tool with zero annotation coverage, this is insufficient behavioral context.

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 states exactly what the tool does with zero wasted words. It's appropriately sized for a simple list operation and front-loads the core functionality.

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?

For a simple list tool with one optional parameter and no output schema, the description provides the basic purpose but lacks important contextual information. Without annotations or output schema, it should explain more about authentication requirements, return format, or behavioral constraints to be truly complete.

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?

The description doesn't mention any parameters, but the input schema has 100% description coverage for its single optional parameter 'opt_fields'. The baseline score of 3 is appropriate since the schema adequately documents the parameter, and the description doesn't need to compensate for gaps.

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 in Asana'), making the purpose immediately understandable. However, it doesn't distinguish this tool from potential sibling list operations (though none exist in the provided sibling list), which prevents a perfect score.

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. There's no mention of prerequisites, context for listing workspaces, or comparison with other workspace-related tools (though none are in the sibling list). This leaves the agent without usage 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/roychri/mcp-server-asana'

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