Skip to main content
Glama
Sign In
io.github.AIops-tools/symantec-clouddlp-aiops

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

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

clouddlp_indices

Read-only

List CloudSOC DLP index health and versions, optionally filtered by index type or limit, to monitor index status and verify available versions.

Instructions

[READ] List DLP index health and versions.

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": "clouddlp_indices"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
index_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

The readOnlyHint annotation already declares this is a safe read, and the "[READ]" prefix merely restates it. The description does add that results cover index health and versions, but says nothing about pagination behavior for the limit, ordering, or how much data a default call returns.

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?

It is a single short sentence with the verb front-loaded and no wasted clauses. However, the "[READ]" tag duplicates the readOnly annotation and the sentence is terse to the point of under-specification rather than being economically concise.

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?

With no output schema, two undocumented parameters, and no annotations beyond readOnly, the description is the only place to explain filtering and return shape, and it does not. An agent knows it lists index health/versions but not how to page, filter, or interpret the result size.

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%, so the description must carry parameter meaning, and it does not. Neither limit (an integer defaulting to 100) nor index_type (a string defaulting to empty) is explained; at best "index" hints that index_type filters by kind, while limit is entirely undocumented.

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

Purpose4/5

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

"List DLP index health and versions" gives a specific verb (List) plus the resource and the data returned (health, versions). It implicitly contrasts with the singular sibling clouddlp_index, which presumably fetches one index, but the description never says so explicitly.

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 explicit when-to-use guidance, no mention of how this differs from clouddlp_index or clouddlp_incident_matches, and no prerequisites. Usage as a listing/discovery call is only implied by the verb "List".

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