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_ssl_initiation

Retrieve an SSL initiation object by its UUID for detailed inspection or management.

Instructions

Get an SSL initiation object 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": {
      "uuid": "<uuid>"
    },
    "name": "sdcloud_get_ssl_initiation"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It implies a read-only operation with no destructive effects, but does not disclose other behavioral aspects such as authentication requirements, rate limits, or what happens if the UUID does not exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that efficiently conveys the core purpose. However, it could benefit from additional structure (e.g., a separate line for context or parameter explanation).

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

Completeness3/5

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

The description is minimal but sufficient for a simple retrieval operation. It does not mention return values or error scenarios, but given the tool's simplicity and the existence of sibling tools for other operations, it covers the essential context.

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 only parameter 'uuid' has no description in the schema and the description merely repeats 'by UUID'. It does not add any meaning beyond what the schema provides (a string identifier). Given 0% schema coverage, the description should elaborate on the parameter's purpose and format.

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 verb 'Get' and the resource 'SSL initiation object' with the identifier method 'by UUID'. It distinguishes itself from sibling tools like 'sdcloud_list_ssl_initiations', 'sdcloud_create_ssl_initiation', etc.

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

Usage Guidelines3/5

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

The description does not provide any guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. For a simple retrieval, the usage is implied but not explicitly clarified.

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