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

hpe-security-director-cloud-mcp

by ddivins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sdcloud_upload_template_workflow_definition

Upload a base64-encoded workflow definition YAML file to create and register a new template for firewall policy management.

Instructions

Upload a workflow definition YAML file to create/register a new template (multipart upload). Provide the YAML content 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": {
      "file_content": "<file_content>"
    },
    "name": "sdcloud_upload_template_workflow_definition"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_nameNoFilename to report for the uploaded definition file.
file_contentYesBase64-encoded workflow definition YAML file content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions multipart upload and base64 encoding but does not disclose side effects (e.g., overwrite behavior), authentication requirements, rate limits, or return format. Given the absence of annotations, this is a significant gap.

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 two short sentences, front-loaded with the verb and purpose. Every word is informative, with no redundancy or fluff.

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?

Given that there is no output schema and no annotations, the description covers input requirements but lacks details on return values, error cases, naming constraints, or idempotency. For a creation tool, this leaves some uncertainty for an agent.

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 100%, so the schema already documents both parameters. The description adds that file_content is base64-encoded YAML, which aligns with the schema description. It does not add additional meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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 (upload), resource (workflow definition YAML file), and action (create/register a new template). It specifies the upload method (multipart) and format (base64-encoded). The tool distinguishes itself from similar sibling tools like sdcloud_upload_template_csv by focusing on YAML content.

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 implies usage when creating/registering a new template via YAML upload, but does not explicitly exclude alternatives or provide when-not-to-use guidance. However, the purpose is clear enough that an agent can infer the appropriate context.

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