Skip to main content
Glama
terrakube-io

Terrakube MCP Server

by terrakube-io

list-variables

Retrieve all variables in a specified workspace within Terrakube MCP Server, using organization and workspace IDs for accurate identification.

Instructions

Lists all variables in the specified workspace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID
workspaceIdYesWorkspace ID

Implementation Reference

  • The handler function that fetches the list of variables from the Terrakube API for the given organization and workspace, then returns the JSON data as formatted text content.
      async ({ organizationId, workspaceId }) => {
        const response = await fetch(`${CONFIG.apiUrl}/organization/${organizationId}/workspace/${workspaceId}/variable`, {
          headers: {
            Authorization: `Bearer ${CONFIG.patToken}`,
            "Content-Type": "application/vnd.api+json"
          }
        });
    
        if (!response.ok) {
          throw new Error(`Failed to list variables: ${response.statusText}`);
        }
    
        const data = await response.json();
        return {
          content: [{
            type: "text",
            text: JSON.stringify(data, null, 2)
          }]
        };
      }
    );
  • Zod input schema defining the required parameters: organizationId and workspaceId.
      organizationId: z.string().describe("Organization ID"),
      workspaceId: z.string().describe("Workspace ID")
    },
  • Registration of the 'list-variables' tool with the MCP server, including name, description, input schema, and handler function.
    server.tool(
      "list-variables",
      "Lists all variables in the specified workspace",
      {
        organizationId: z.string().describe("Organization ID"),
        workspaceId: z.string().describe("Workspace ID")
      },
      async ({ organizationId, workspaceId }) => {
        const response = await fetch(`${CONFIG.apiUrl}/organization/${organizationId}/workspace/${workspaceId}/variable`, {
          headers: {
            Authorization: `Bearer ${CONFIG.patToken}`,
            "Content-Type": "application/vnd.api+json"
          }
        });
    
        if (!response.ok) {
          throw new Error(`Failed to list variables: ${response.statusText}`);
        }
    
        const data = await response.json();
        return {
          content: [{
            type: "text",
            text: JSON.stringify(data, null, 2)
          }]
        };
      }
    );
  • src/index.ts:25-25 (registration)
    Invocation of registerVariableTools which registers the 'list-variables' tool (among others) to the main MCP server instance.
    registerVariableTools(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 for behavioral disclosure. It states the tool lists variables but doesn't describe return format (e.g., array structure, pagination), permissions required, rate limits, or whether it's read-only (implied but not confirmed). For a tool with zero annotation coverage, this leaves significant behavioral gaps unaddressed.

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 immediately conveys the core functionality without unnecessary words. It's appropriately sized for a simple list operation and front-loads the essential information. Every word earns its place with no redundancy or fluff.

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 100% schema coverage but no annotations and no output schema, the description provides basic completeness. It states what the tool does but lacks details about return values, behavioral constraints, and usage context. The description is minimally adequate but leaves the agent to infer important operational aspects.

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 clearly documented in the schema. The description adds no additional parameter information beyond what the schema provides (it mentions 'specified workspace' but doesn't elaborate on parameter usage or relationships). Baseline 3 is appropriate when the schema does all the parameter documentation work.

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 ('Lists') and resource ('all variables in the specified workspace'), making the tool's purpose immediately understandable. It distinguishes itself from siblings like 'get-variable' (singular retrieval) and 'list-modules' (different resource type), though it doesn't explicitly contrast with other list operations. The description avoids tautology by specifying scope beyond just the tool name.

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 valid organization/workspace IDs), compare with 'get-variable' for single variable retrieval, or explain when listing variables is appropriate versus other list operations like 'list-modules'. Usage context is implied but not explicitly stated.

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