Skip to main content
Glama
Ollikell

hpe-security-director-cloud-mcp

by Ollikell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

sdcloud_list_ca_certificates

List CA certificates across the fleet with optional pagination, filtering, and sorting to locate specific certificates or audit their presence.

Instructions

List CA certificates across the fleet, 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.8/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 correctly indicates a read-only operation (listing) but does not disclose any additional behavioral traits (e.g., pagination limits, performance, or consistency guarantees). No contradiction.

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?

One sentence clearly conveys the core action and optional features (pagination, filtering, sorting). No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description addresses the tool's purpose adequately. It covers fleet-wide scope and optional capabilities. However, it could hint at the return structure (e.g., list of certificate objects) to improve completeness.

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 only adds 'optional' qualifier, which is implied by the schema. Baseline 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 explicitly states 'List CA certificates across the fleet,' using a specific verb and resource. The phrase 'across the fleet' distinguishes this tool from sibling 'sdcloud_list_device_ca_certificates,' which lists per device.

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 implicitly suggests fleet-wide listing but does not provide explicit when-to-use or when-not-to-use guidance. There is no mention of alternatives like per-device listing, though the sibling tools exist.

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