Skip to main content
Glama
Sign In
MCP Datadog Server

MCP Datadog Server

by ClaudioLazaro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create_security_vulnerabilities_notification_rules

Set up automated alerts for security vulnerabilities in your systems to receive immediate notifications when threats are detected.

Instructions

Create a new notification rule for security vulnerabilities and return the created rule.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 the full burden. It states 'Create a new notification rule' and 'return the created rule', implying a write operation with a return value, but lacks details on permissions, side effects, error handling, or rate limits. This is a significant gap for a mutation tool with zero annotation coverage.

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 front-loads the action and outcome with zero waste. It's appropriately sized for a tool with no parameters, making it easy to parse.

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?

Given the complexity of creating a notification rule (a mutation), the lack of annotations, and no output schema, the description is incomplete. It doesn't explain what a 'notification rule' entails, how it's configured, or what the return value includes. For a tool in a security context, more detail is needed to guide effective use.

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 input schema has 0 parameters with 100% schema description coverage, so no parameters need documentation. The description doesn't mention any parameters, which is appropriate. Baseline is 4 for zero parameters, as there's nothing to compensate for.

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 verb ('Create') and resource ('notification rule for security vulnerabilities'), making the purpose specific and understandable. It distinguishes from siblings by focusing on security vulnerabilities rather than other notification types like 'monitor_notification_rules' or 'security_signals_notification_rules', though it doesn't explicitly contrast them.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'create_monitor_notification_rules' and 'create_security_signals_notification_rules', there's no indication of the specific context for security vulnerabilities, prerequisites, or exclusions. Usage is implied only by the name and description.

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