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_device_image

Deploy a software image definition to devices and obtain a job ID to monitor deployment progress.

Instructions

Deploy a single software image definition to its target device(s). Returns a job id; poll sdcloud_get_deploy_image_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": {
      "image_uuid": "<image_uuid>",
      "body": "<body>"
    },
    "name": "sdcloud_deploy_device_image"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided. Describes async nature (returns job id, polling needed) but does not disclose authorization needs, destructive potential, or error conditions.

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 concise sentences with clear action and follow-up step. No redundancy.

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

Completeness3/5

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

Describes purpose and async pattern, but missing details on required body schema and return value structure. Adequate for a simple deploy tool but could be more comprehensive given nested object parameter.

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%. Description adds no parameter-level detail beyond schema; fails to explain 'image_uuid' or structure of 'body'.

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?

Clearly states action (deploy), resource (software image definition), and target (device(s)). Distinguishes from siblings like sdcloud_bulk_deploy_device_image and sdcloud_get_deploy_image_status.

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?

Implies usage through 'single' vs 'bulk' sibling, but lacks explicit when-to-use or when-not-to-use guidance. No comparison with other deploy tools.

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