Skip to main content
Glama
Sign In
MCP Datadog Server

MCP Datadog Server

by ClaudioLazaro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_security_monitoring_configuration_suppressions_rule

Retrieve suppression rules for a specific security monitoring rule ID to manage alert filtering and reduce noise in Datadog security monitoring.

Instructions

Get the list of suppressions that affect a specific existing rule by its ID.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool retrieves a list, implying a read-only operation, but doesn't disclose behavioral traits like authentication requirements, rate limits, pagination, or error conditions. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose. It is front-loaded with the core action and includes necessary detail about the rule ID. There is no wasted verbiage, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters and no output schema, the description is minimally adequate but incomplete. It explains what the tool does but lacks details on behavior, usage context, or output format. For a tool with zero annotations and no output schema, more context would be helpful, but it meets the basic threshold.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage. The description mentions retrieving suppressions 'by its ID', implying a rule ID is needed, but since there are no parameters, this is likely handled differently (e.g., via URL path). With no parameters, the baseline is 4, as the description adds context about the rule ID without conflicting with the schema.

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 clearly states the action ('Get the list of suppressions') and the target resource ('that affect a specific existing rule by its ID'). It specifies verb+resource+scope, though it doesn't explicitly differentiate from sibling tools like 'get_security_monitoring_configuration_suppressions' which likely lists all suppressions rather than those for a specific rule.

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?

No guidance on when to use this tool versus alternatives is provided. The description mentions retrieving suppressions for a 'specific existing rule by its ID', but doesn't clarify prerequisites (e.g., needing a rule ID) or contrast with similar tools like 'get_security_monitoring_configuration_suppressions' (which might list all suppressions).

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