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

hpe-security-director-cloud-mcp

by ddivins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sdcloud_deploy_template

Deploy a configuration template to its mapped devices, returning a job ID to poll for deployment progress.

Instructions

Deploy a configuration template to its mapped devices. Returns a job id; poll sdcloud_get_template_deploy_status for progress.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It states the tool deploys a template and returns a job id, but does not mention destructive potential, required permissions, side effects, or what constitutes a successful deployment. The lack of depth for a mutation operation is a significant gap.

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 sentences, front-loaded with purpose, no unnecessary verbiage. Efficient and to the point.

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 the tool's complexity (deploying a template with a nested body parameter), the absence of an output schema, and missing annotations, the description is too minimal. It does not explain 'mapped devices,' how to interpret the job id, or what the body should contain. Compare to sdcloud_deploy_site (not seen but likely more detailed), this lacks completeness.

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

Parameters2/5

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

Schema description coverage is 50% (body has a description, template_id lacks one). The tool description adds no parameter details; it does not explain what template_id or body are beyond the schema. The body's schema reference is vague, and the description does not compensate for the missing template_id 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: 'Deploy a configuration template to its mapped devices.' This distinguishes it from sibling tools like sdcloud_get_template, sdcloud_delete_template, etc., which are about other template operations.

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

Usage Guidelines3/5

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

The description provides a usage hint: 'Returns a job id; poll sdcloud_get_template_deploy_status for progress.' However, it does not specify when to use this tool versus other deploy tools (e.g., sdcloud_deploy_site, sdcloud_deploy_firewall_policy), nor does it give exclusions or alternatives.

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