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_template_preview_result_by_device

Retrieve the per-device result of a template preview job to verify configuration changes for a specific device.

Instructions

Get the per-device result of a template preview 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": {
      "preview_id": "<preview_id>",
      "device_id": "<device_id>"
    },
    "name": "sdcloud_get_template_preview_result_by_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_idYes
preview_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 provided. Description does not disclose whether the operation is read-only (likely, given 'get'), any side effects, authorization requirements, or rate limits. For a data retrieval tool, such context is important but missing.

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?

Extremely concise (single phrase), but lacks proper sentence structure. It conveys purpose efficiently but misses opportunities for better formatting (e.g., bullet points, parameter clarifications).

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?

No output schema, no annotations, and minimal description. The agent lacks information about return values, error conditions, or how the per-device result relates to the overall preview job. Incomplete for a data retrieval tool with no structured documentation.

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 adds no information about the parameters, which are only named 'preview_id' and 'device_id'. It does not explain their format, source, or expected values, leaving the agent with no cues beyond the names.

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?

Description clearly states the verb 'Get', the resource 'per-device result', and the context 'template preview job'. It distinguishes from sibling tools like sdcloud_get_template_preview_status (overall status) and sdcloud_get_template_deploy_result_by_device (deploy, not preview).

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 vs alternatives (e.g., sdcloud_get_template_preview_status for overall status, sdcloud_get_template_validate_result_by_device for validation). No mention of prerequisites like needing a valid preview_id from a prior preview job.

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