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_reusable_pattern

Read-only

Retrieve a specific version of a reusable CloudSOC DLP pattern by pattern ID to inspect detection logic and support DLP configuration review.

Instructions

[READ] Read a reusable DLP pattern version.

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": {
      "pattern_id": "<pattern_id>"
    },
    "name": "clouddlp_reusable_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNo
pattern_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, and the '[READ]' prefix merely restates it, adding no context. The description says nothing about what happens with the default version value, whether a missing pattern errors, or what the returned payload contains.

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

Conciseness4/5

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

A single front-loaded sentence with zero filler and no repetition. It is efficient, though its brevity borders on under-specification for a two-parameter tool.

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 two undocumented parameters, no output schema, and no annotations beyond readOnlyHint, the definition leaves key questions unanswered. An agent cannot determine identifier format or how version selection works from this text.

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% for both parameters, so the description carries the full burden and fails to compensate. 'Version' hints that versioned retrieval exists, but neither pattern_id's identifier format nor the meaning of version=0 (default/latest) is explained anywhere.

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?

The description names a specific verb ('Read') and resource ('reusable DLP pattern version'), so an agent knows this retrieves a pattern-level object. It does not explicitly contrast with the plural sibling clouddlp_reusable_patterns, though the singular name plus 'version' implies a single-record fetch.

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 guidance on when to use this versus clouddlp_reusable_patterns or clouddlp_profile, nor any prerequisite or exclusion. The '[READ]' tag implies read-only usage but nothing routes the agent between fetching one pattern and 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