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

hpe-security-director-cloud-mcp

by ddivins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sdcloud_delete_ips_profile_rule

Delete an IPS rule from a profile to manage intrusion prevention settings.

Instructions

Delete an IPS rule within an IPS profile.

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": {
      "profile_uuid": "<profile_uuid>",
      "rule_uuid": "<rule_uuid>"
    },
    "name": "sdcloud_delete_ips_profile_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
rule_uuidYes
profile_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior1/5

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

With no annotations provided, the description must disclose behavioral traits. It only states the action without mentioning irreversibility, permissions, side effects, or impact on other profiles, leaving the agent with no insight into the operation's implications.

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

Conciseness3/5

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

The description is a single sentence, which is concise but lacks substantive detail to justify its brevity. It could include more context without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of the sibling tools and the absence of output schema and annotations, the description is wholly incomplete. It fails to provide sufficient information for an agent to use the tool effectively in context.

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

Parameters1/5

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

Schema description coverage is 0%. The description does not explain the purpose or origin of the parameters (profile_uuid, rule_uuid), failing to compensate for the lack of schema documentation.

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 (Delete) and the resource (IPS rule within an IPS profile). It effectively distinguishes from related siblings like sdcloud_delete_ips_profile and sdcloud_create_ips_profile_rule.

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 is provided on when to use this tool versus alternatives (e.g., sdcloud_delete_ips_profile_exempt_rule or sdcloud_delete_ips_signature). There is no mention of prerequisites, dependencies, or usage context.

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