Skip to main content
Glama

get_cluster_info

Retrieve cluster details like name, ID, software version, and node count from Cohesity DataProtect for data protection management and monitoring.

Instructions

Get Cohesity cluster information including name, ID, software version, and node count

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function for 'get_cluster_info' tool that fetches cluster information by calling client.getV2('cluster') and returns the JSON-formatted result. Includes error handling that returns an error message if the API call fails.
    async () => {
      try {
        const cluster = await client.getV2("cluster");
        return toolResult(JSON.stringify(cluster, null, 2));
      } catch (error) {
        return toolResult(`Error fetching cluster info: ${error}`, true);
      }
    },
  • Tool registration using server.tool() which defines the tool name 'get_cluster_info', description, empty schema object (no parameters), and the async handler function.
    server.tool(
      "get_cluster_info",
      "Get Cohesity cluster information including name, ID, software version, and node count",
      {},
      async () => {
        try {
          const cluster = await client.getV2("cluster");
          return toolResult(JSON.stringify(cluster, null, 2));
        } catch (error) {
          return toolResult(`Error fetching cluster info: ${error}`, true);
        }
      },
    );
  • Empty schema object {} indicating the tool accepts no input parameters.
    {},
  • CohesityClient.getV2() method that constructs and executes the GET request to the Cohesity V2 API endpoint. Used by the handler to fetch cluster information.
    async getV2(
      path: string,
      params?: Record<string, string>,
    ): Promise<unknown> {
      return this.request("GET", `${this.baseUrlV2}/${path}`, undefined, params);
    }
  • src/index.ts:43-43 (registration)
    Top-level registration where registerClusterTools is called with the MCP server instance and CohesityClient to register all cluster tools including 'get_cluster_info'.
    registerClusterTools(server, client);
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. It states what information is returned but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or whether the data is cached/live. For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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?

Single sentence, front-loaded with the core purpose, zero wasted words. Every element ('Get Cohesity cluster information including...') directly contributes to understanding what the tool does. Efficiently structured for immediate comprehension.

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?

Given 0 parameters, 100% schema coverage, and no output schema, the description adequately covers the tool's purpose and return content. However, it lacks context about behavioral aspects (e.g., permissions, freshness) and usage guidelines relative to siblings. For a simple read tool, this is minimally viable but leaves room for improvement in guiding the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description appropriately doesn't discuss parameters, focusing instead on the output content. Baseline for 0 parameters is 4, as no parameter semantics are needed beyond what the schema provides.

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 ('Get') and resource ('Cohesity cluster information') with specific attributes listed (name, ID, software version, node count). It distinguishes from siblings like 'get_cluster_stats' by focusing on static configuration rather than performance metrics. However, it doesn't explicitly contrast with all siblings, preventing a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, timing considerations, or comparisons to sibling tools like 'get_cluster_stats' (for metrics) or 'list_sources' (for inventory). The agent must infer usage from the tool name and description 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

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/fredriksknese/mcp-cohesity'

If you have feedback or need assistance with the MCP directory API, please join our Discord server