Skip to main content
Glama
ddivins

hpe-security-director-cloud-mcp

by ddivins

sdcloud_list_ips_signatures

Retrieve IPS signature objects with pagination, filtering, and sorting to manage security policies.

Instructions

List IPS signature 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.
Behavior3/5

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

With no annotations, the description carries the full burden. It mentions optional pagination, filtering, and sorting, but does not disclose behavior like default pagination, maximum limits, or that it is read-only. Adds some value but insufficient for full transparency.

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?

Single sentence with no wasted words. Front-loaded with the core purpose. Every word earns its place.

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 optional parameters, the description provides a basic overview but lacks details on return format, data scope, or side effects. Adequate but not rich enough for a complete understanding.

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 baseline is 3. The description does not add extra meaning beyond stating that pagination, filtering, and sorting are optional. No additional parameter details or examples.

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 IPS signature objects' with optional pagination, filtering, and sorting. It is a specific verb-resource combination that distinguishes this tool from sibling list tools targeting other resources.

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_list_ips_signature_categories or other listing tools. No when-not-to-use or context provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ddivins/hpe-security-director-cloud-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server