Skip to main content
Glama
terrakube-io

Terrakube MCP Server

by terrakube-io

list-workspaces

Retrieve all workspaces within a specified organization using the Terrakube MCP Server. Manage infrastructure efficiently by accessing and organizing workspace details.

Instructions

Lists all workspaces in the specified organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID

Implementation Reference

  • Handler function for 'list-workspaces' tool that fetches workspaces from the API for the given organizationId and returns JSON-formatted data.
    async ({ organizationId }) => {
      const response = await fetch(`${CONFIG.apiUrl}/organization/${organizationId}/workspace`, {
        headers: {
          Authorization: `Bearer ${CONFIG.patToken}`,
          "Content-Type": "application/vnd.api+json"
        }
      });
    
      if (!response.ok) {
        throw new Error(`Failed to list workspaces: ${response.statusText}`);
      }
    
      const data = await response.json();
      return {
        content: [{
          type: "text",
          text: JSON.stringify(data, null, 2)
        }]
      };
    }
  • Input schema for 'list-workspaces' tool using Zod, requiring an organizationId string.
    {
      organizationId: z.string().describe("Organization ID")
    },
  • Registers the 'list-workspaces' tool on the MCP server, including name, description, input schema, and handler function.
    server.tool(
      "list-workspaces",
      "Lists all workspaces in the specified organization",
      {
        organizationId: z.string().describe("Organization ID")
      },
      async ({ organizationId }) => {
        const response = await fetch(`${CONFIG.apiUrl}/organization/${organizationId}/workspace`, {
          headers: {
            Authorization: `Bearer ${CONFIG.patToken}`,
            "Content-Type": "application/vnd.api+json"
          }
        });
    
        if (!response.ok) {
          throw new Error(`Failed to list workspaces: ${response.statusText}`);
        }
    
        const data = await response.json();
        return {
          content: [{
            type: "text",
            text: JSON.stringify(data, null, 2)
          }]
        };
      }
    );
  • src/index.ts:23-23 (registration)
    Top-level call to registerWorkspaceTools in the main server setup, which registers the 'list-workspaces' tool among others.
    registerWorkspaceTools(server);
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 action without disclosing behavioral traits. It doesn't mention whether this is a read-only operation, if it requires specific permissions, what the output format is, or any rate limits. This leaves significant gaps for a tool with no annotation coverage.

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 zero waste. It's front-loaded with the core purpose and appropriately sized for a simple list operation, 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 simplicity (1 parameter, 100% schema coverage) but lack of annotations and output schema, the description is incomplete. It doesn't explain return values, pagination, error handling, or behavioral context, which are crucial for an AI agent to use it correctly without structured guidance.

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 100%, so the schema already documents the single parameter 'organizationId'. The description adds minimal value by implying the parameter's role ('specified organization') but doesn't provide additional syntax, format details, or constraints beyond what the schema offers.

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 verb ('Lists') and resource ('all workspaces'), specifying the scope ('in the specified organization'). It distinguishes from siblings like 'list-organizations' by focusing on workspaces, though it doesn't explicitly contrast with 'get-workspace' or 'create-workspace'.

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 like 'get-workspace' for a single workspace or 'create-workspace' for adding new ones. It lacks explicit when/when-not instructions or prerequisites, relying solely on the implied context of listing.

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

Related 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/terrakube-io/mcp-server-terrakube'

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