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_firewall_policy_state

Check the deployment state of a firewall policy to determine if it is up to date, pending, or out of sync. Identify synchronization issues.

Instructions

Get the deployment state of a firewall policy (e.g. up to date, pending, out of sync).

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>"
    },
    "name": "sdcloud_get_firewall_policy_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
policy_uuidYes
include_assigned_devicesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations provided, the description must convey behavioral traits. It correctly implies a read-only operation through 'Get', but does not disclose potential effects, auth requirements, or rate limits. The examples of states are helpful but insufficient for complete transparency.

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 that is front-loaded with the core action and includes concrete examples, making it efficient. However, it could include parameter details without sacrificing conciseness, slightly lowering the score.

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 no output schema, no annotations, and two parameters with 0% coverage, the description is severely incomplete. It does not explain return values, parameter roles, or usage patterns, leaving the agent with insufficient information to invoke the tool correctly.

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 coverage is 0%, meaning the description must explain parameter meaning. However, the description does not mention 'policy_uuid' (required) or 'include_assigned_devices', adding no value beyond the schema itself. This is a critical gap for agent invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool retrieves the deployment state of a firewall policy, with examples like 'up to date, pending, out of sync'. It effectively distinguishes from sibling tools like sdcloud_get_firewall_policy (configuration) and sdcloud_deploy_firewall_policy (action) through the specific verb 'Get' and resource 'deployment state'.

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. There is no mention of prerequisites, such as having deployed the policy first, or exclusions, like not using it to check configuration. The description lacks context for when an agent should invoke this tool.

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