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_policy_deploy_job_device_status

Retrieve the deployment status for a specific device from a bulk policy deploy job to verify policy application results.

Instructions

Get the per-device result of a bulk policy deploy job.

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": {
      "deploy_id": "<deploy_id>",
      "device_id": "<device_id>"
    },
    "name": "sdcloud_get_policy_deploy_job_device_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOptional result format, e.g. text or json.
deploy_idYes
device_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 carry the full burden. It does not disclose any behavioral traits such as whether it is read-only, idempotent, or requires specific authorization. The minimal description fails to inform the agent of side effects or constraints.

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 concise as a single sentence, but it lacks structure and additional details that would be helpful. It is under-specified for a tool with three parameters.

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 complexity (3 parameters, no output schema, many sibling tools), the description is too minimal. It does not explain the return value format, prerequisites, or how the result relates to the deploy job 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 coverage is only 33% (only format has a description). The description does not add any meaning to the parameters; required parameters deploy_id and device_id are not described. With low coverage, the description should compensate but does not.

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 verb 'Get' and the specific resource 'per-device result of a bulk policy deploy job'. It distinguishes from sibling tools like sdcloud_get_policy_deploy_job (overall job status) and sdcloud_get_policy_selective_deploy_job_device_status (selective deploy).

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 on when to use this tool versus alternatives. There is no indication that it should be used after starting a bulk deploy job or how it relates to related tools. The description only states what it does without 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