Skip to main content
Glama
terrakube-io

Terrakube MCP Server

by terrakube-io

create-workspace

Generate a new workspace in a specified organization with defined Terraform version, name, and optional VCS settings using the Terrakube MCP Server.

Instructions

Creates a new workspace in the specified organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNoWorkspace description
nameYesWorkspace name
organizationIdYesOrganization ID
terraformVersionYesTerraform version
vcsProviderNoVCS provider (e.g., github, gitlab)
vcsRepoNoVCS repository URL

Implementation Reference

  • The asynchronous handler function that implements the core logic of the 'create-workspace' tool. It sends a POST request to the Terrakube API endpoint to create a new workspace using the provided organizationId, name, description, terraformVersion, vcsProvider, and vcsRepo, then returns the JSON response.
    async ({ organizationId, name, description, terraformVersion, vcsProvider, vcsRepo }) => {
      const response = await fetch(`${CONFIG.apiUrl}/organization/${organizationId}/workspace`, {
        method: "POST",
        headers: {
          Authorization: `Bearer ${CONFIG.patToken}`,
          "Content-Type": "application/vnd.api+json"
        },
        body: JSON.stringify({
          data: {
            type: "workspace",
            attributes: {
              name,
              description,
              terraformVersion,
              vcsProvider,
              vcsRepo
            }
          }
        })
      });
    
      if (!response.ok) {
        throw new Error(`Failed to create workspace: ${response.statusText}`);
      }
    
      const data = await response.json();
      return {
        content: [{
          type: "text",
          text: JSON.stringify(data, null, 2)
        }]
      };
    }
  • Zod input schema defining the parameters for the 'create-workspace' tool: organizationId (required), name (required), description (optional), terraformVersion (required), vcsProvider (optional), vcsRepo (optional).
    {
      organizationId: z.string().describe("Organization ID"),
      name: z.string().describe("Workspace name"),
      description: z.string().optional().describe("Workspace description"),
      terraformVersion: z.string().describe("Terraform version"),
      vcsProvider: z.string().optional().describe("VCS provider (e.g., github, gitlab)"),
      vcsRepo: z.string().optional().describe("VCS repository URL")
    },
  • The server.tool() registration call for the 'create-workspace' tool within the registerWorkspaceTools function, specifying name, description, input schema, and handler.
    server.tool(
      "create-workspace",
      "Creates a new workspace in the specified organization",
      {
        organizationId: z.string().describe("Organization ID"),
        name: z.string().describe("Workspace name"),
        description: z.string().optional().describe("Workspace description"),
        terraformVersion: z.string().describe("Terraform version"),
        vcsProvider: z.string().optional().describe("VCS provider (e.g., github, gitlab)"),
        vcsRepo: z.string().optional().describe("VCS repository URL")
      },
      async ({ organizationId, name, description, terraformVersion, vcsProvider, vcsRepo }) => {
        const response = await fetch(`${CONFIG.apiUrl}/organization/${organizationId}/workspace`, {
          method: "POST",
          headers: {
            Authorization: `Bearer ${CONFIG.patToken}`,
            "Content-Type": "application/vnd.api+json"
          },
          body: JSON.stringify({
            data: {
              type: "workspace",
              attributes: {
                name,
                description,
                terraformVersion,
                vcsProvider,
                vcsRepo
              }
            }
          })
        });
    
        if (!response.ok) {
          throw new Error(`Failed to create workspace: ${response.statusText}`);
        }
    
        const data = await response.json();
        return {
          content: [{
            type: "text",
            text: JSON.stringify(data, null, 2)
          }]
        };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states this is a creation operation, implying it's a write/mutation, but doesn't disclose behavioral traits like required permissions, whether the workspace is immediately active, error conditions, or what happens on duplicate names. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 action and resource, making it easy to parse. Every word earns its place by specifying the tool's purpose concisely.

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 this is a mutation tool with 6 parameters, no annotations, and no output schema, the description is incomplete. It lacks behavioral context (e.g., side effects, permissions), doesn't explain the return value, and provides minimal guidance. The high schema coverage helps, but the description doesn't compensate for the missing structural information.

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 all 6 parameters with descriptions. The description adds no additional meaning beyond implying 'organizationId' is required for context, but doesn't explain parameter relationships or usage nuances. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('creates') and resource ('new workspace'), and specifies the context ('in the specified organization'). It distinguishes from obvious non-siblings like 'edit-workspace' or 'get-workspace', but doesn't explicitly differentiate from other creation tools like 'create-organization' or 'create-module' beyond the resource type.

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. It doesn't mention prerequisites (e.g., needing an existing organization), exclusions, or compare with sibling tools like 'edit-workspace' for updates or 'list-workspaces' for viewing. Usage is implied by the verb 'creates' but lacks explicit 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

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