hpe-security-director-cloud-mcp

sdcloud_bulk_move_nat_policy_rules

Bulk-move NAT policy rules to a target rule group and position, enabling efficient reorganization of rule order and hierarchy.

Instructions

Bulk-move NAT policy rules to a target rule group/position. Body: rule_ids, target_rule_group_id, position.

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

Input Schema

Name	Required	Description	Default
`body`	Yes	JSON request body matching the target Security Director Cloud schema.
`policy_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description should cover behavioral traits. It mentions the body fields but does not disclose effects (e.g., whether rules are removed from original group, order changes, idempotency, error scenarios). A bare minimum would indicate the operation is atomic or partially applicable.

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?

Two sentences, front-loaded with the action. No filler, but the second sentence listing body fields is helpful. Could be slightly more structured but very efficient.

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?

The description is too sparse for a bulk operation with no annotations or output schema. Missing details like required policy_id, constraints on rule_ids (e.g., same policy), response behavior, and error handling. Incomplete for a reliable agent invocation.

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

Parameters4/5

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

The description explicitly lists the expected fields inside the body (rule_ids, target_rule_group_id, position), adding meaning beyond the schema's generic 'JSON request body matching...' description. This helps the agent understand what to pass despite the schema's low coverage.

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 action (bulk-move), resource (NAT policy rules), and destination (target rule group/position). It distinguishes from siblings like sdcloud_move_nat_policy_rule_groups which moves groups, and sdcloud_bulk_move_firewall_policy_rules which deals with firewall rules.

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 vs alternatives, no prerequisites or exclusions. The description is purely declarative without any context about use cases or when not to use.

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

Deploy Server