hpe-security-director-cloud-mcp

sdcloud_install_device_license

Install a license on a device by uploading a base64-encoded license file. Supports primary and secondary license files for standalone or l2_cluster devices.

Instructions

Install a license on a device (multipart upload). Provide at least one of a primary license file (license_file_content) or, for an l2_cluster secondary device, a secondary license file (secondary_license_file_content), each base64-encoded.

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_install_device_license"
  }
}

Input Schema

Name	Required	Description
`device_uuid`	Yes
`license_file_name`	No	Filename to report for the primary license file.
`license_file_content`	No	Base64-encoded license text file content for a standalone device.
`secondary_license_file_name`	No	Filename to report for the secondary license file.
`secondary_license_file_content`	No	Base64-encoded license text file content for the secondary device in an l2_cluster.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the behavioral disclosure. It mentions 'multipart upload' which hints at a file upload operation, but does not specify if the operation is synchronous or asynchronous, whether it replaces existing licenses, or what permissions are needed. The presence of sdcloud_get_install_license_status suggests async behavior, but it's not mentioned.

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 short sentences containing all necessary information without redundancy. Every word adds value.

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

Completeness4/5

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

Given no output schema or annotations, the description is fairly complete. It covers the tool's purpose, the key parameters, and the conditions for using them. It could mention the asynchronous nature or how to check status, but overall it provides a solid understanding of how to use the tool.

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

Parameters4/5

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

Schema coverage is 80% (4 of 5 parameters have descriptions), but the description adds significant context: it explains the purpose of each content parameter (primary vs secondary), that they must be base64-encoded, and the condition that at least one must be provided. This goes beyond the schema's basic descriptions.

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 ('Install a license on a device'), specifies it's a multipart upload, and distinguishes between primary and secondary license files for standalone vs l2_cluster secondary devices. This differentiates it from sibling tools like sdcloud_get_install_license_status.

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

Usage Guidelines4/5

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

The description provides explicit guidance on when to use each parameter: provide at least one of license_file_content (for standalone) or secondary_license_file_content (for l2_cluster secondary device). It lacks explicit 'when not to use' but the conditions are clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server