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

hpe-security-director-cloud-mcp

by ddivins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sdcloud_start_policy_cleanup_job

Removes unused objects and rules from multiple firewall and NAT policies by starting a bulk cleanup job. Acts across all policies in the request, unlike single-policy cleanup tools.

Instructions

Start a bulk cleanup job across multiple policies, removing unused objects/rules. Operates across ALL policies (both firewall and NAT) referenced in the request body, unlike the single-policy sdcloud_{deploy,preview,cleanup,selective_deploy}_{firewall,nat}_policy tools, which act on one policy_id at a time.

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": {
      "body": "<body>"
    },
    "name": "sdcloud_start_policy_cleanup_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesJSON request body matching the target Security Director Cloud schema.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions it removes unused objects/rules (indicating destructive action) but lacks details on authorization needs, whether the job is asynchronous, or any side effects. For a mutation tool, this is insufficient.

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?

Two concise sentences with no wasted words. The first sentence states the core purpose, and the second provides crucial differentiation from sibling tools. Front-loaded and efficient.

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 the tool's complexity (bulk cleanup, no output schema, async likely), the description is missing details on job tracking, return values, and how the cleanup is performed. It provides enough to initiate use but not to fully understand the lifecycle. Could mention checking status via sdcloud_get_policy_cleanup_job.

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?

The single parameter 'body' has 100% schema coverage, so the baseline is 3. The description adds minimal value by stating it matches the target schema but does not provide examples, constraints, or clarification on how to structure the body for bulk cleanup across policies.

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 tool starts a bulk cleanup job across multiple policies, removing unused objects/rules. It explicitly distinguishes itself from single-policy sibling tools like sdcloud_cleanup_firewall_policy or sdcloud_deploy_nat_policy, providing a specific verb and resource scope.

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

Usage Guidelines4/5

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

The description explicitly contrasts this bulk tool with single-policy alternatives, guiding agents to use this when affecting multiple policies. However, it does not explicitly state when to avoid using it (e.g., if only one policy needs cleanup) or provide other usage conditions.

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