Skip to main content
Glama
terrakube-io

Terrakube MCP Server

by terrakube-io

create-organization

Generate a new organization with a specified name and optional description using the Terrakube MCP Server. Simplifies infrastructure management by enabling organized setup and configuration.

Instructions

Creates a new organization with the specified name and optional description

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNoOrganization description
nameYesOrganization name

Implementation Reference

  • The async handler function that executes the tool logic: constructs JSON payload with organization data and sends POST request to API endpoint.
    async ({ name, description = "" }) => {
      const body = JSON.stringify({
        data: {
          type: "organization",
          attributes: {
            name,
            description
          }
        }
      });
    
      const response = await fetch(`${CONFIG.apiUrl}/organization`, {
        method: "POST",
        headers: {
          Authorization: `Bearer ${CONFIG.patToken}`,
          "Content-Type": "application/vnd.api+json"
        },
        body: body
      });
    
      if (response.status === 201) {
        const data = await response.json();
        return {
          content: [{
            type: "text",
            text: JSON.stringify(data, null, 2)
          }]
        };
      } else {
        throw new Error(`Failed to create organization: ${response.statusText}`);
      }
    }
  • Zod input schema defining required 'name' and optional 'description' parameters for the tool.
    {
      name: z.string().describe("Organization name"),
      description: z.string().optional().describe("Organization description")
    },
  • MCP server.tool() call that registers the 'create-organization' tool with its description, schema, and handler.
    server.tool(
      "create-organization",
      "Creates a new organization with the specified name and optional description",
      {
        name: z.string().describe("Organization name"),
        description: z.string().optional().describe("Organization description")
      },
      async ({ name, description = "" }) => {
        const body = JSON.stringify({
          data: {
            type: "organization",
            attributes: {
              name,
              description
            }
          }
        });
    
        const response = await fetch(`${CONFIG.apiUrl}/organization`, {
          method: "POST",
          headers: {
            Authorization: `Bearer ${CONFIG.patToken}`,
            "Content-Type": "application/vnd.api+json"
          },
          body: body
        });
    
        if (response.status === 201) {
          const data = await response.json();
          return {
            content: [{
              type: "text",
              text: JSON.stringify(data, null, 2)
            }]
          };
        } else {
          throw new Error(`Failed to create organization: ${response.statusText}`);
        }
      }
    );
  • src/index.ts:22-22 (registration)
    Invocation of registerOrganizationTools in the main server setup, which includes registration of the create-organization tool.
    registerOrganizationTools(server);
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 of behavioral disclosure. While 'Creates' implies a mutation, it lacks critical details: required permissions, whether the operation is idempotent, what happens on duplicate names, or the response format. For a creation 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 that front-loads the core purpose. Every word earns its place, with no redundant or vague phrasing. It's appropriately sized for a simple creation tool with two parameters.

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 of a creation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects (e.g., permissions, idempotency), output details, or error conditions. The schema covers parameters well, but the overall context for safe and effective use is lacking.

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%, with both parameters ('name' and 'description') documented in the schema. The description adds minimal value by noting that 'description' is optional, but this is already implied by the schema's required fields. It doesn't provide additional context like naming constraints or description formatting beyond what the schema specifies.

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 ('a new organization'), specifying what the tool does. It distinguishes from siblings like 'edit-organization' by focusing on creation rather than modification. However, it doesn't explicitly differentiate from other 'create-' tools (e.g., create-module, create-workspace) 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., permissions), when not to use it, or how it relates to siblings like 'edit-organization' or 'list-organizations'. The agent must infer usage from the name alone.

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