Skip to main content
Glama
Ollikell

hpe-security-director-cloud-mcp

by Ollikell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

sdcloud_list_device_groups

Retrieve a paginated, filterable, sortable list of device groups for targeted security management.

Instructions

List device groups with optional pagination, filtering, and sorting.

Input Schema

TableJSON 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

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only mentions optional features but lacks details on authentication, rate limits, default pagination, or whether it returns full objects or summaries.

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?

Extremely concise and front-loaded single sentence. However, it could be slightly more informative while maintaining brevity.

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?

No output schema, so description should explain return format. It does not mention what the response contains (list of device group objects). Also fails to differentiate from sdcloud_get_device_group for single retrieval.

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 baseline is 3. The description adds context of pagination/filtering/sorting but no additional meaning beyond what the schema already provides for each parameter.

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 tool lists device groups, with optional pagination, filtering, and sorting. It distinguishes itself from sibling CRUD tools like sdcloud_get_device_group, sdcloud_create_device_group, etc.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives like sdcloud_get_device_group for a single group. Does not mention prerequisites or context for pagination/filtering options.

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