List CloudSOC DLP profiles to inspect configured data protection policies and support read-only DLP auditing.
[READ] List DLP profiles.
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_profiles"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| query | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already declares this is a safe read, so the [READ] prefix adds no new information. Nothing is said about result volume, pagination, ordering, or how the query narrows results, which is the behavioral context an agent would actually need.
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?
A single short sentence with no wasted words and the resource named up front. However, the brevity is under-specification rather than efficiency — the size reflects missing content, not tight writing.
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?
No output schema and no annotations beyond readOnlyHint, so the description must carry the load and doesn't. For a simple unbounded list tool this is minimally viable, but an agent cannot predict result shape or filtering behavior.
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 0%, so the schema's bare 'query' string with default "" carries no meaning, and the description does not say what the query matches against (profile name, pattern, label). One optional param is low stakes, but the description adds nothing at all.
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?
States a specific verb and resource ("List DLP profiles") and the [READ] tag frames it as a retrieval operation. Against siblings like clouddlp_profile (singular) it is reasonably distinguishable, though it never explicitly says "returns all profiles" versus a single-profile fetch.
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?
No guidance on when to use this list tool versus clouddlp_profile or clouddlp_profile_history, and no mention of what the query parameter filters or whether results are paginated. The agent must infer usage entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.