mcp-cohesity

list_recovery_tasks

Retrieve recovery tasks with status, type, and progress details, filtered by environment or time range.

Instructions

List Cohesity recovery tasks with status, type, and progress 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_recovery_tasks"
  }
}

Input Schema

Name	Required	Description
`status`	No	Filter recovery tasks by status
`environments`	No	Filter by source environment type
`start_time_usecs`	No	Filter tasks created after this Unix timestamp in microseconds
`end_time_usecs`	No	Filter tasks created before this Unix timestamp in microseconds
`max_results`	No	Maximum number of results to return

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 12, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Without annotations, the description must disclose behavioral traits. It only states the tool lists tasks with basic fields. It does not mention pagination, authorization needs, rate limits, or what happens without filters. The default max_results is not mentioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, 10 words, no redundancy. It is front-loaded with purpose. However, it could be slightly more informative without losing conciseness.

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?

For a tool with 5 parameters and no output schema or annotations, the description is too sparse. It omits important context like default results, ordering, time filter expectations, and pagination behavior.

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 all parameters. The description adds only that the tool returns 'status, type, and progress', which is generic. With full schema coverage, baseline is 3.

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?

Description clearly states the verb 'List', the resource 'Cohesity recovery tasks', and the information returned ('status, type, and progress'). This distinguishes it from siblings like 'get_recovery_task' (singular) and other listing tools for different resources.

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 on when to use this tool versus alternatives. While siblings like 'get_recovery_task' handle individual tasks, the description does not mention this or provide any when/not-to-use criteria.

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

Deploy Server