Skip to main content
Glama
Sign In
hpe-security-director-cloud-mcp

hpe-security-director-cloud-mcp

by ddivins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sdcloud_change_password

Change the password for the currently authenticated user. Old credentials are invalidated immediately to secure your account.

Instructions

WARNING: Sensitive/destructive-ish action. Changes the password of the currently authenticated user. This immediately invalidates the old credentials for that account — confirm intent before calling.

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": {
      "body": "<body>"
    },
    "name": "sdcloud_change_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesJSON request body matching the target Security Director Cloud schema.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Discloses that the action 'immediately invalidates the old credentials', which is critical behavioral information. With no annotations, the description carries the full burden and provides useful context about irreversibility.

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 sentences that are direct and front-loaded with the warning and action. No unnecessary words; every sentence adds value.

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?

Despite clear purpose and sensitivity warning, the tool has a single complex parameter with no structure guidance and no output schema. The description does not compensate for this, leaving the agent without enough information to use the tool correctly.

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 description omits any details about the required 'body' parameter, which is an opaque object. Schema coverage is 100% but only gives a vague description. The agent has no guidance on what fields (e.g., old/new password) to include, making correct invocation difficult.

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?

Clearly states 'Changes the password of the currently authenticated user' with a specific verb and resource. Distinguishes from all sibling tools, which are about firewall policies, IPsec, devices, etc., none of which handle password changes.

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?

Explicitly warns 'Sensitive/destructive-ish action' and says 'confirm intent before calling', guiding careful use. Does not mention alternatives, but no other tool directly competes for password changes.

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