mcp-cohesity

list_protection_groups

List backup jobs with status, schedule, and last run details. Filter by name, environment, or paused state to monitor data protection.

Instructions

List Cohesity protection groups (backup jobs) with status, schedule, and last run information

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description
`name`	No	Filter protection groups by name (partial match)
`environment`	No	Filter by environment type (e.g., kVMware, kPhysical, kNas, kSQL)
`is_active`	No	Filter by active/inactive state
`is_paused`	No	Filter by paused state
`max_results`	No	Maximum number of results to return

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 12, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description must fully convey behavior. It does not disclose whether the operation is read-only, whether pagination applies, or what the response format looks like. The agent cannot infer safety or limitations beyond the listed output fields.

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, focused sentence with no extraneous information. Every word adds value.

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 5 parameters, no output schema, and no annotations, the description is adequate but incomplete. It does not explain pagination behavior, response format, or default ordering, which are important for a list 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?

All 5 parameters have descriptions in the schema (100% coverage), so the description does not need to add detail. However, the description adds no additional context beyond what the schema provides, such as default sorting or interaction between filters.

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 'List', the resource 'Cohesity protection groups (backup jobs)', and includes what information is returned (status, schedule, last run). It distinguishes from sibling tools like get_protection_group (single group) and list_protection_runs (runs).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for overview of protection groups but does not explicitly state when to use this tool versus alternatives like get_protection_group for detailed info or list_protection_runs for runs. No exclusions or prerequisites are mentioned.

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

Deploy Server