Skip to main content
Glama
Ollikell

hpe-security-director-cloud-mcp

by Ollikell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

sdcloud_list_applications

List application objects with flexible pagination, filtering, and sorting. Retrieve counts or item details to manage security application inventory efficiently.

Instructions

List application objects 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

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It indicates a read operation (list) and mentions optional features, but does not disclose response format, pagination behavior, or any specific constraints beyond what the schema already conveys.

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?

A single, clear sentence with no redundant information. Every word adds value and the structure is efficient.

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 no output schema and 5 parameters, the description is minimal. It does not describe the structure of returned application objects or pagination limits. While sufficient for basic understanding, it lacks detail for more complex scenarios.

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?

The input schema has 100% coverage with descriptions for all parameters. The description adds a high-level summary ('optional pagination, filtering, and sorting') but does not provide 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 the verb 'List', the resource 'application objects', and the optional features 'pagination, filtering, and sorting'. It effectively distinguishes from sibling list tools that operate on different resources.

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 (when you need to list applications) from the name and description, but it does not provide explicit guidance on when not to use it or suggest alternatives (e.g., for single application retrieval, use sdcloud_get_application).

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