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

hpe-security-director-cloud-mcp

by ddivins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sdcloud_list_swp_profiles

Retrieve SWP profile lists with pagination, filtering, and sorting to manage SSL/Web Proxy security objects.

Instructions

List SWP (SSL/Web Proxy) profile objects with optional pagination, filtering, and sorting.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sdcloud_list_swp_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoStarting index for pagination (zero-based). Default 0.
sizeNoMax results per page. 0 returns the API-imposed maximum.
countNoIf true, return only the total count, no item details.
sortbyNoSort field, e.g. sortby=(name(descending)).
filtersNoFilter conditions to apply to the results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden but only mentions optional pagination, filtering, and sorting. It does not disclose potential side effects, performance characteristics, or response structure, leaving moderate gaps.

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, well-structured sentence of 15 words that conveys the core purpose without redundancy, earning top marks for efficiency.

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?

Without an output schema or annotations, the description does not detail return values or expected behavior beyond object listing. For a 5-param tool with optional features, it is adequate but could provide more context like example usage.

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 description coverage is 100%, so the schema already documents all parameters. The description adds no extra parameter meaning beyond what is in the schema, scoring the baseline 3.

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 uses a specific verb 'List' and clearly defines the resource as 'SWP (SSL/Web Proxy) profile objects', distinguishing it from other list tools for different profile types like list_ips_profiles or list_ssl_proxy_profiles.

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 implies usage for listing SWP profiles with optional pagination, filtering, and sorting, but does not provide explicit guidance on when to use this tool versus alternatives like list_ips_profiles or when not to use it.

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