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

hpe-security-director-cloud-mcp

by ddivins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sdcloud_create_firewall_policy_rule_in_group

Create a firewall rule within a specific policy rule group, defining its name, action, sources, destinations, and applications.

Instructions

Create a rule inside a firewall policy rule group. Body typically includes name, description, action, sources, destinations, applications.

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_uuid": "<policy_uuid>",
      "scope": "<scope>",
      "group_uuid": "<group_uuid>",
      "body": "<body>"
    },
    "name": "sdcloud_create_firewall_policy_rule_in_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesJSON request body matching the target Security Director Cloud schema.
scopeYesRule scope: 'global' or 'zone'.
group_uuidYes
policy_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so description must carry the full burden. It only says 'Create a rule' without disclosing side effects, required permissions, whether the change requires deployment, or what happens on success. Minimal disclosure.

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 and resource. No redundancy. Could be slightly more structured but 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?

Missing details on return values, error handling, relationship to deployment, and how the rule interacts with the policy group. Given no output schema and only 50% schema coverage, the description is incomplete for a creation 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?

Schema coverage is 50% with two parameters (group_uuid, policy_uuid) undescribed. The description adds value by listing typical body fields (name, description, action, sources, destinations, applications) beyond the schema's vague 'JSON request body matching the target Security Director Cloud schema.' However, it does not fully compensate for the missing parameter descriptions.

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 'Create a rule inside a firewall policy rule group' and lists typical body fields. It distinguishes from sibling tools like sdcloud_create_firewall_policy_rule (creates a rule not in a group) and sdcloud_create_firewall_policy_rule_group (creates the group).

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 explicit guidance on when to use this tool versus alternatives such as sdcloud_create_firewall_policy_rule (which creates a rule without a group context). No prerequisites or exclusions 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

Other Tools