Skip to main content
Glama
Sign In
hpe-security-director-cloud-mcp

hpe-security-director-cloud-mcp

by ddivins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sdcloud_get_policy_cleanup_job

Retrieve the current status of a bulk policy cleanup job using its cleanup ID. Monitor progress and completion of policy cleanup tasks.

Instructions

Get the status of a bulk policy cleanup job by cleanup_id.

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": {
      "cleanup_id": "<cleanup_id>"
    },
    "name": "sdcloud_get_policy_cleanup_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
cleanup_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 disclose behavioral traits. It only says 'Get the status' but does not mention that this is a read-only operation, whether it can be called repeatedly, or what side effects (if any) exist. The description adds minimal behavioral context beyond the obvious.

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?

The description is a single sentence of 11 words, which is appropriately concise. It includes the core action and key parameter. However, it could be more informative while still being concise.

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 absence of an output schema, the description should at least indicate what the response contains (e.g., status fields, progress, etc.). It does not. The tool is simple but the description is incomplete for an agent to fully understand the tool's behavior.

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

Parameters2/5

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

The input schema has one required parameter (cleanup_id) with no description (0% coverage). The description mentions 'by cleanup_id' but does not explain its format, source, or constraints (e.g., where to obtain it). This leaves the agent with insufficient information to correctly construct the parameter.

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 it gets the status of a bulk policy cleanup job using a cleanup_id. It distinguishes from siblings like sdcloud_get_policy_cleanup_job_device_status (which gets per-device status) and sdcloud_start_policy_cleanup_job (which starts the job). The verb 'Get' and resource 'status of bulk policy cleanup job' are specific.

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 that this tool is to be used after a cleanup job has been started, to check its status. However, it does not provide explicit guidance on when to use it versus alternatives, nor does it mention any prerequisites or expected sequence (e.g., calling start first). No 'when not to use' information is given.

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