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_device

Retrieve a device's complete details by UUID from Security Director Cloud. Use this tool to access device data for network management.

Instructions

Get a single device by UUID.

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": {
      "device_uuid": "<device_uuid>"
    },
    "name": "sdcloud_get_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are present, and the description does not disclose behavioral traits beyond the obvious 'Get' operation. There is no mention of side effects, permissions, data freshness, or response format. The burden falls entirely on the description, which is insufficient.

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 very short and front-loaded with the key action. However, it is too brief to provide sufficient context. While conciseness is valued, it sacrifices clarity and completeness. An additional sentence would improve it without losing structure.

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 that there is no output schema and the tool is part of a large SDK with many sibling tools, the description is incomplete. It does not indicate the return value (e.g., device details) or any related operations. A basic 'Get' operation should at least hint at what fields are returned.

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?

The single parameter 'device_uuid' is only described in the schema (type: string). The description adds no extra meaning, such as the format of the UUID, where to obtain it, or any constraints. With 0% schema description coverage, the description fails to compensate.

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 the verb 'Get' and the resource 'device' with a method of identification ('by UUID'). It effectively conveys the tool's primary function, though it does not distinguish it from other device-related tools like sdcloud_list_devices.

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 usage guidelines are provided. The description does not specify when to use this tool over alternatives (e.g., sdcloud_list_devices) or any prerequisites. An agent would need additional knowledge to decide when to call this function.

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