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_secintel_profiles

List SecIntel profiles from Security Director Cloud with pagination, filtering, and sorting options.

Instructions

List SecIntel 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_secintel_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

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions optional pagination and filtering but does not disclose default page size, maximum results, response format, or potential performance implications.

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?

Single sentence with no fluff. However, it lacks a structured breakdown or front-loading of key actions. Still concise and clear.

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; description does not explain response format, default pagination behavior, or how to construct filter expressions. For a 5-parameter list tool, the description is incomplete for effective use.

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% with detailed descriptions for each parameter. The description summarizes 'optional pagination, filtering, and sorting' but adds no new meaning beyond the schema.

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 'List SecIntel profile objects' with optional pagination, filtering, and sorting. It differentiates from sibling tools like 'sdcloud_get_secintel_profile' (single) and 'sdcloud_list_secintel_profiles_groups' (groups).

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 versus alternatives (e.g., get for a single profile, list_groups for groups). No mention of when to apply pagination or filtering parameters.

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