hpe-security-director-cloud-mcp

sdcloud_list_subscription_associations

List associations like sites and devices for a subscription, with pagination, filtering, and sorting capabilities.

Instructions

List associations (e.g. sites/devices) for a subscription, with optional pagination, filtering, and sorting.

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": {
      "subscription_uuid": "<subscription_uuid>"
    },
    "name": "sdcloud_list_subscription_associations"
  }
}

Input Schema

Name	Required	Description
`from`	No	Starting index for pagination (zero-based). Default 0.
`size`	No	Max results per page. 0 returns the API-imposed maximum.
`sortby`	No	Sort field, e.g. sortby=(name(descending)).
`filters`	No	Filter conditions to apply to the results.
`subscription_uuid`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the tool is read-only, authentication requirements, rate limits, or effects beyond listing. For a read operation, it should at least indicate it is non-destructive.

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, clear sentence that is front-loaded with the core purpose. Every word is necessary, and no extraneous information is included.

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?

For a list tool with no output schema, the description is adequate but minimal. It does not explain the return structure (e.g., paginated list) or any limitations. More detail would help an agent understand the expected response format.

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?

With schema coverage at 80%, most parameters are already described in the schema. The description adds only generic mention of pagination, filtering, and sorting, without providing additional meaning beyond the schema definitions.

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 it lists associations for a subscription, with specific examples (sites/devices) and mentions optional pagination, filtering, and sorting. This distinguishes it from sibling tools like sdcloud_list_subscriptions, which lists subscriptions themselves.

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 associations, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., sdcloud_create_subscription_association for creating). No when-not or alternative tools are mentioned.

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

Deploy Server