Skip to main content
Glama
terrakube-io

Terrakube MCP Server

by terrakube-io

get-module

Retrieve detailed information about a specific module by providing the module ID and organization ID within the Terrakube MCP Server infrastructure.

Instructions

Retrieves detailed information about a specific module

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moduleIdYesModule ID
organizationIdYesOrganization ID

Implementation Reference

  • The handler function that implements the 'get-module' tool logic: fetches detailed information about a specific module from the Terrakube API using the provided organizationId and moduleId, parses the JSON response, and returns it formatted as text content.
    async ({ organizationId, moduleId }) => {
      const response = await fetch(`${CONFIG.apiUrl}/organization/${organizationId}/module/${moduleId}`, {
        headers: {
          Authorization: `Bearer ${CONFIG.patToken}`,
          "Content-Type": "application/vnd.api+json"
        }
      });
    
      if (!response.ok) {
        throw new Error(`Failed to get module: ${response.statusText}`);
      }
    
      const data = await response.json();
      return {
        content: [{
          type: "text",
          text: JSON.stringify(data, null, 2)
        }]
      };
    }
  • Zod input schema for the 'get-module' tool, defining required string parameters organizationId and moduleId with descriptions.
    {
      organizationId: z.string().describe("Organization ID"),
      moduleId: z.string().describe("Module ID")
    },
  • Direct registration of the 'get-module' tool on the MCP server using server.tool(), including name, description, schema, and handler.
    server.tool(
      "get-module",
      "Retrieves detailed information about a specific module",
      {
        organizationId: z.string().describe("Organization ID"),
        moduleId: z.string().describe("Module ID")
      },
      async ({ organizationId, moduleId }) => {
        const response = await fetch(`${CONFIG.apiUrl}/organization/${organizationId}/module/${moduleId}`, {
          headers: {
            Authorization: `Bearer ${CONFIG.patToken}`,
            "Content-Type": "application/vnd.api+json"
          }
        });
    
        if (!response.ok) {
          throw new Error(`Failed to get module: ${response.statusText}`);
        }
    
        const data = await response.json();
        return {
          content: [{
            type: "text",
            text: JSON.stringify(data, null, 2)
          }]
        };
      }
    );
  • src/index.ts:24-24 (registration)
    Higher-level registration call to registerModuleTools(server) in the main server setup, which includes the 'get-module' tool.
    registerModuleTools(server);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'retrieves' information, implying a read-only operation, but doesn't clarify aspects like authentication needs, rate limits, error handling, or what 'detailed information' includes. For a 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 wasted words. It's front-loaded with the core action ('Retrieves') and resource ('module'), making it easy to parse. Every word earns its place by conveying essential purpose without redundancy.

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 complexity (2 required parameters, no output schema, no annotations), the description is incomplete. It lacks details on return values, error cases, or behavioral constraints, leaving the agent with insufficient context to use it effectively beyond basic invocation. A read operation should at least hint at the data structure returned.

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?

The input schema has 100% description coverage, with clear parameter names and types. The description adds no additional semantic context beyond implying 'moduleId' identifies the module and 'organizationId' might scope it, but this is already inferred from the schema. Baseline 3 is appropriate as 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 verb ('Retrieves') and resource ('detailed information about a specific module'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'list-modules' or 'get-organization', which would require mentioning it fetches a single module by ID rather than listing multiple.

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 like needing a module ID, contrast with 'list-modules' for browsing, or specify use cases like viewing module details after listing. This leaves the agent to infer usage from context 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