Skip to main content
Glama
Sign In
mcp-cohesity

mcp-cohesity

by fredriksknese
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_protection_group

Retrieve detailed configuration, schedule, and last run status for a specific Cohesity protection group to assess backup health and operations.

Instructions

Get detailed information about a specific Cohesity protection group including configuration, schedule, and last run status

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_protection_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesProtection group ID
include_last_run_infoNoInclude information about the last backup run

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations exist, so the description must disclose behavioral traits. It states it gets details but does not mention that it is a read-only operation, any potential side effects, or performance considerations. The description adds minimal transparency beyond basic function.

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?

A single, front-loaded sentence with 15 words, no redundant information. Every word contributes to understanding the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (two parameters, one required) and no output schema, the description covers key return content (configuration, schedule, last run status). It lacks details on error handling or edge cases, but is largely complete for a read tool.

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 both parameters. The description adds context by mentioning 'last run status', which relates to include_last_run_info, but does not elaborate on parameter meaning or usage beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 the resource 'protection group', and specifies what details are included (configuration, schedule, last run status). It distinguishes itself from sibling tools like list_protection_groups (which lists multiple groups) and get_protection_run (which targets runs).

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 like list_protection_groups or run_protection_group. There is no mention of prerequisites or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools