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_data_identifier

Read-only

Retrieves a single DLP data identifier by its ID, enabling review of classification settings and detection patterns.

Instructions

[READ] Read one data identifier.

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": {
      "identifier_id": "<identifier_id>"
    },
    "name": "clouddlp_data_identifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifier_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

The "[READ]" prefix merely restates the supplied readOnlyHint=true annotation, adding no new information. With annotations already covering the safety profile, the description still omits error behavior for missing IDs, permission requirements, and what the response contains.

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?

The single sentence is front-loaded and free of filler, so nothing needs trimming. But its brevity is under-specification rather than efficient communication, since key context is simply absent.

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?

For a lookup tool with one undocumented parameter, no output schema, and a bare readOnlyHint, the description leaves the agent guessing about ID provenance and return shape. The annotation covers safety only, so the description should carry more of the burden than it does.

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?

The single required parameter identifier_id has 0% schema description coverage, so the schema supplies only a type. The description does not clarify whether this ID comes from the list tool, an index, or a profile, leaving the only parameter effectively undocumented.

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?

"Read one data identifier" gives a verb (read) and a resource (data identifier), and the singular "one" implicitly contrasts with the sibling list tool clouddlp_data_identifiers. However, it never explains what a data identifier is in DLP terms, so an agent unfamiliar with the domain cannot tell what object it retrieves.

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 and no mention of alternatives, despite a large sibling set (clouddlp_data_identifiers, clouddlp_incidents, clouddlp_profiles). The agent must infer from the singular noun that this fetches one item versus listing many.

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