Skip to main content
Glama
terrakube-io

Terrakube MCP Server

by terrakube-io

edit-workspace

Modify workspace details such as name, Terraform version, VCS provider, repository URL, and description in the Terrakube MCP Server for streamlined infrastructure management.

Instructions

Updates an existing workspace's details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNoNew workspace description
nameNoNew workspace name
organizationIdYesOrganization ID
terraformVersionNoNew Terraform version
vcsProviderNoNew VCS provider
vcsRepoNoNew VCS repository URL
workspaceIdYesWorkspace ID

Implementation Reference

  • The async handler function for the 'edit-workspace' tool that performs a PATCH request to the API to update the workspace details.
    async ({ organizationId, workspaceId, name, description, terraformVersion, vcsProvider, vcsRepo }) => {
      const response = await fetch(`${CONFIG.apiUrl}/organization/${organizationId}/workspace/${workspaceId}`, {
        method: "PATCH",
        headers: {
          Authorization: `Bearer ${CONFIG.patToken}`,
          "Content-Type": "application/vnd.api+json"
        },
        body: JSON.stringify({
          data: {
            type: "workspace",
            id: workspaceId,
            attributes: {
              name,
              description,
              terraformVersion,
              vcsProvider,
              vcsRepo
            }
          }
        })
      });
    
      if (response.status === 204) {
        return {
          content: [{
            type: "text",
            text: "Workspace updated successfully"
          }]
        };
      } else {
        throw new Error(`Failed to update workspace: ${response.statusText}`);
      }
    }
  • Zod input schema defining parameters for the 'edit-workspace' tool, including organizationId, workspaceId, and optional attributes to update.
    {
      organizationId: z.string().describe("Organization ID"),
      workspaceId: z.string().describe("Workspace ID"),
      name: z.string().optional().describe("New workspace name"),
      description: z.string().optional().describe("New workspace description"),
      terraformVersion: z.string().optional().describe("New Terraform version"),
      vcsProvider: z.string().optional().describe("New VCS provider"),
      vcsRepo: z.string().optional().describe("New VCS repository URL")
    },
  • The server.tool() call that registers the 'edit-workspace' tool with its name, description, input schema, and handler function.
    server.tool(
      "edit-workspace",
      "Updates an existing workspace's details",
      {
        organizationId: z.string().describe("Organization ID"),
        workspaceId: z.string().describe("Workspace ID"),
        name: z.string().optional().describe("New workspace name"),
        description: z.string().optional().describe("New workspace description"),
        terraformVersion: z.string().optional().describe("New Terraform version"),
        vcsProvider: z.string().optional().describe("New VCS provider"),
        vcsRepo: z.string().optional().describe("New VCS repository URL")
      },
      async ({ organizationId, workspaceId, name, description, terraformVersion, vcsProvider, vcsRepo }) => {
        const response = await fetch(`${CONFIG.apiUrl}/organization/${organizationId}/workspace/${workspaceId}`, {
          method: "PATCH",
          headers: {
            Authorization: `Bearer ${CONFIG.patToken}`,
            "Content-Type": "application/vnd.api+json"
          },
          body: JSON.stringify({
            data: {
              type: "workspace",
              id: workspaceId,
              attributes: {
                name,
                description,
                terraformVersion,
                vcsProvider,
                vcsRepo
              }
            }
          })
        });
    
        if (response.status === 204) {
          return {
            content: [{
              type: "text",
              text: "Workspace updated successfully"
            }]
          };
        } else {
          throw new Error(`Failed to update workspace: ${response.statusText}`);
        }
      }
    );
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. 'Updates' implies a mutation, but it doesn't disclose behavioral traits like required permissions, whether changes are reversible, rate limits, or what happens to unspecified fields. For a mutation tool with zero annotation coverage, this is a significant gap.

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 appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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 complexity (mutation tool with 7 parameters, no annotations, no output schema), the description is incomplete. It doesn't cover behavioral aspects, usage context, or output expectations, leaving significant gaps for an AI agent to understand how to invoke it correctly.

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 7 parameters. The description adds no meaning beyond what the schema provides—it doesn't explain parameter relationships, constraints, or usage context. Baseline 3 is appropriate when 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 ('Updates') and resource ('an existing workspace's details'), making the purpose understandable. It distinguishes from 'create-workspace' by specifying 'existing', but doesn't differentiate from other edit tools like 'edit-module' or 'edit-organization' 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 organizationId and workspaceId), when not to use it, or how it differs from other edit tools in the sibling list beyond the resource name.

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