io.github.AIops-tools/symantec-clouddlp-aiops

clouddlp_incidents

Read-only

Search bounded DLP incidents within a date range to review CloudSOC security events; supports optional limit and cursor pagination.

Instructions

[READ] Search bounded DLP incidents.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "clouddlp_incidents"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`end_date`	Yes
`start_date`	Yes
`cursor_json`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, so '[READ]' and 'Search' add nothing new. With annotations covering the safety profile, the description should disclose pagination via cursor_json, default/max limit behavior, or result volume, and it says nothing about any of these.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words, which is structurally sound. But the brevity comes at the cost of under-specification rather than achieved concision, so it cannot score higher.

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?

Placeholder justification

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description carries the full burden and mostly fails it. 'Bounded' gives a faint signal that start_date/end_date delimit the query, but date format, limit semantics, and the cursor_json pagination contract are entirely undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Search' and resource 'DLP incidents' are specific, and '[READ]' flags the operation class. However, 'bounded' is the only hint at scope and the description never distinguishes this list/search tool from the sibling clouddlp_incident_matches, which an agent could easily confuse it with.

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?

There is no when-to-use guidance, no mention of prerequisites, and no named alternative such as clouddlp_incident_matches for drill-down. 'Bounded' weakly implies a required date range, but the agent must infer that from the schema's required fields rather than the prose.

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

Deploy Server