hpe-security-director-cloud-mcp

sdcloud_install_device_local_certificate

Installs a local certificate and private key on a device by providing base64-encoded files and a pass phrase, associating the certificate with a given certificate ID.

Instructions

Install a local certificate and its private key on a device (multipart upload). Provide the certificate id to associate, the certificate and key files as base64, and the pass phrase used to encrypt the key file.

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>",
      "certificate_id": "<certificate_id>",
      "local_certificate_content": "<local_certificate_content>",
      "local_certificate_key_file_content": "<local_certificate_key_file_content>",
      "pass_phrase": "<pass_phrase>"
    },
    "name": "sdcloud_install_device_local_certificate"
  }
}

Input Schema

Name	Required	Description
`device_uuid`	Yes
`pass_phrase`	Yes	Pass phrase used to encrypt/decrypt the private key file.
`certificate_id`	Yes	Unique identifier of the certificate to associate with the installed local certificate.
`local_certificate_content`	Yes	Base64-encoded local certificate file content.
`local_certificate_file_name`	No	Filename to report for the certificate file.
`local_certificate_key_file_name`	No	Filename to report for the private key file.
`local_certificate_key_file_content`	Yes	Base64-encoded private key file content corresponding to the local certificate.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full transparency burden. It states 'Install' (write operation) but does not disclose side effects (e.g., overwriting existing certificate, device restart needs), permissions required, or error handling behavior. The mention of multipart upload is a technical detail, but behavioral consequences are missing.

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?

The description is a single 24-word sentence. It is concise and front-loaded with the action and resource. Every word contributes meaning without redundancy.

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 (7 params, no output schema, no annotations), the description is incomplete. It does not explain the return value, error cases, idempotency, or whether installation triggers any device changes. The agent lacks information about success/failure indicators, which is critical for a state-changing operation.

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

Parameters3/5

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

Schema coverage is 86% (6 of 7 params have descriptions). The description adds context by summarizing key parameters (certificate_id, base64 files, pass phrase) and noting multipart upload. However, the optional file name parameters are omitted in the description, and the schema already provides adequate explanations. The description adds moderate value beyond the schema.

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 action (Install) and resource (local certificate and private key on a device). It mentions multipart upload. While it does not explicitly differentiate from sibling sdcloud_install_device_ca_certificate, the distinction is implied by the resource type. The verb+resource combination is specific and unambiguous.

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?

The description lists required inputs but provides no guidance on when to use this tool versus alternative certificate operations (e.g., installing a CA certificate, deleting a certificate). It lacks prerequisites, prohibitions, or context for selection among siblings like sdcloud_install_device_ca_certificate.

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

Deploy Server