Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

ListDowntimes

Retrieve active scheduled downtimes for Datadog monitoring. Filter by current status, include related resources, and manage pagination for focused downtime insights.

Instructions

Get all scheduled downtimes.

Query Parameters:

  • current_only: Only return downtimes that are active when the request is made.

  • include: Comma-separated list of resource paths for related resources to include in the response. Supported resource paths are created_by and monitor.

  • page[offset]: Specific offset to use as the beginning of the returned page.

  • page[limit]: Maximum number of downtimes in the response.

Responses:

  • 200 (Success): OK

    • Content-Type: application/json

    • Response Properties:

      • data: An array of downtimes.

      • included: Array of objects related to the downtimes.

    • Example:

{
  "data": [
    "unknown_type"
  ],
  "included": [
    "unknown_type"
  ],
  "meta": "unknown_type"
}
  • 403: Forbidden

    • Content-Type: application/json

    • Response Properties:

      • errors: A list of errors.

    • Example:

{
  "errors": [
    "Bad Request"
  ]
}
  • 429: Too many requests

    • Content-Type: application/json

    • Response Properties:

      • errors: A list of errors.

    • Example:

{
  "errors": [
    "Bad Request"
  ]
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
current_onlyNoOnly return downtimes that are active when the request is made.
includeNoComma-separated list of resource paths for related resources to include in the response. Supported resource paths are `created_by` and `monitor`.
page[limit]NoMaximum number of downtimes in the response.
page[offset]NoSpecific offset to use as the beginning of the returned page.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoAn array of downtimes.
metaNo
includedNoArray of objects related to the downtimes.
Behavior3/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 of behavioral disclosure. It adds some useful context: it describes pagination behavior via 'page[offset]' and 'page[limit]', includes error responses (403, 429), and mentions that responses include JSON with 'data' and 'included' arrays. However, it doesn't cover important aspects like rate limits, authentication requirements, or whether the operation is idempotent or safe.

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

Conciseness2/5

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

The description is overly verbose and poorly structured. It includes extensive details about HTTP responses (200, 403, 429) with examples and properties, which are redundant since an output schema exists. The core purpose is buried under unnecessary technical details. A more concise version would focus on the tool's intent and usage, leaving response formats to the structured schema.

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

Completeness4/5

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

Given that there's an output schema (implied by 'Has output schema: true'), the description doesn't need to explain return values in detail. It covers the basic purpose, parameters, and some behavioral aspects like pagination and error responses. However, it lacks guidance on usage relative to siblings and doesn't fully address behavioral transparency gaps (e.g., auth, rate limits). For a list operation with good schema coverage, this is mostly complete but could be improved.

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?

The schema description coverage is 100%, meaning all parameters are well-documented in the schema itself. The description repeats the parameter information in the 'Query Parameters' section, which adds no new semantic value beyond what's already in the schema. This meets the baseline score of 3 for high schema coverage, but doesn't provide additional insights like parameter interactions or usage examples.

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 tool's purpose: 'Get all scheduled downtimes.' This is a specific verb ('Get') and resource ('scheduled downtimes'), making it easy to understand. However, it doesn't explicitly distinguish this tool from its sibling 'GetDowntime' (which likely retrieves a single downtime), leaving some ambiguity about when to use one over the other.

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. It doesn't mention the sibling tool 'GetDowntime' or explain that this tool is for listing multiple downtimes while 'GetDowntime' is for retrieving a specific one. There's also no information about prerequisites, authentication, or typical use cases.

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

Related 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/brukhabtu/datadog-mcp'

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