Retrieve available IPS anomaly tests, optionally filtered by service, to inspect read-only reference data for intrusion prevention.
List available IPS anomaly tests (read-only reference data), optionally filtered by service.
| Name | Required | Description | Default |
|---|---|---|---|
| from | No | Starting index for pagination (zero-based). Default 0. | |
| size | No | Max results per page. | |
| service | No | Filter anomaly tests by service. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description adds 'read-only reference data' which clarifies safety, but lacks details on pagination, ordering, or response format. With no annotations, more behavioral context would be beneficial.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence of 12 words, no redundancy. Efficient, but could be structured with bullet points to add more detail (e.g., pagination defaults).
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple list operation with no output schema, but lacks hints about response fields. Could be more complete given the absence of output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%; description adds that 'service' is an optional filter. This provides minor additional meaning beyond schema, meeting baseline for high coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the verb 'List', resource 'IPS anomaly tests', and notes it is read-only reference data, optionally filtered by service. This distinguishes it from sibling list tools like sdcloud_list_ips_profiles.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage as a read-only list, but does not explicitly guide when to use this tool over alternatives such as sdcloud_list_ips_profiles or sdcloud_list_ips_services. No when-not-to-use or prerequisites mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.