Skip to main content
Glama
us-all

datadog-mcp-server

by us-all

create-downtime

Schedule a downtime to mute monitors by scope, monitor ID, or tags. Specify start and end times, timezone, and notification message.

Instructions

Create a downtime to mute monitors by scope, monitor ID, or monitor tags

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeYesDowntime scope. Example: env:prod or host:web-01 or * (all)
startYesStart time as Unix epoch seconds. Example: 1740000000
endNoEnd time as Unix epoch seconds (omit for indefinite). Example: 1740003600
messageNoNotification message. Example: Scheduled maintenance window
monitorIdNoSpecific monitor ID to mute. Example: 12345678
monitorTagsNoMute monitors matching these tags. Example: ["service:api"]
timezoneNoIANA timezone. Example: UTC or America/New_YorkUTC
notifyEndStatesNoStates to notify on end. Example: ["alert", "warn"]
Behavior3/5

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

With no annotations, the description carries full burden but only states that it mutes monitors, lacking details on side effects (e.g., overlapping downtimes, recurring behavior, or idempotency).

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 clear sentence with no redundant content, perfectly front-loaded.

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 no output schema and no annotations, the description lacks completeness by not explaining the return value, confirmation, or what happens after creation. It covers basic purpose but leaves gaps.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description adds no new parameter meaning beyond the schema, but it reinforces the purpose by highlighting the three filtering methods.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (create), resource (downtime), and purpose (mute monitors by scope, monitor ID, or monitor tags). It effectively distinguishes from sibling tools like 'cancel-downtime' and 'mute-monitor'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use cases by listing filtering options but does not explicitly guide when to use this tool versus alternatives like 'mute-monitor' or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/us-all/datadog-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server