Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

GetDowntime

Retrieve downtime details by specifying a downtime ID, including related resources like monitor or creator, through the Datadog MCP Server API. Simplify downtime tracking and analysis.

Instructions

Get downtime detail by downtime_id.

Path Parameters:

  • downtime_id (Required): ID of the downtime to fetch.

Query Parameters:

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

Responses:

  • 200 (Success): OK

    • Content-Type: application/json

    • Response Properties:

      • included: Array of objects related to the downtime that the user requested.

    • Example:

{
  "data": "unknown_type",
  "included": [
    "unknown_type"
  ]
}
  • 400: Bad Request

    • Content-Type: application/json

    • Response Properties:

      • errors: A list of errors.

    • Example:

{
  "errors": [
    "Bad Request"
  ]
}
  • 403: Forbidden

    • Content-Type: application/json

    • Response Properties:

      • errors: A list of errors.

    • Example:

{
  "errors": [
    "Bad Request"
  ]
}
  • 404: Not Found

    • 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
downtime_idYesID of the downtime to fetch.
includeNoComma-separated list of resource paths for related resources to include in the response. Supported resource paths are `created_by` and `monitor`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
includedNoArray of objects related to the downtime that the user requested.
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It includes HTTP response codes (e.g., 200, 400, 403, 404, 429) and error handling details, which adds some context beyond basic functionality. However, it doesn't cover critical aspects like authentication requirements, rate limits, or whether the operation is idempotent, leaving significant gaps for a tool that likely involves sensitive data access.

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 HTTP response details and examples that are redundant with the output schema, cluttering the core information. Sentences like 'Get downtime detail by `downtime_id`.' are front-loaded, but the bulk of the text doesn't earn its place, making it inefficient for quick comprehension by an AI agent.

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's complexity (2 parameters, 1 required) and the presence of an output schema, the description is somewhat complete but has gaps. It covers basic functionality and error responses, but without annotations, it misses behavioral traits like security or performance considerations. The output schema reduces the need to explain return values, but the description still lacks guidance on usage and sibling differentiation, making it only minimally adequate.

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 the input schema already fully documents both parameters ('downtime_id' and 'include'). The description repeats this information in the 'Path Parameters' and 'Query Parameters' sections without adding new meaning or examples beyond what's in the schema. This meets the baseline score of 3, as the schema does the heavy lifting, but no extra value is provided.

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 downtime detail by `downtime_id`.' It specifies the verb ('Get') and resource ('downtime detail'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'ListDowntimes' or 'GetIncident', which would require a more specific comparison to achieve a score of 5.

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 sibling tools like 'ListDowntimes' for listing multiple downtimes or 'GetIncident' for related incident data, nor does it specify prerequisites or exclusions. This lack of contextual usage information limits its effectiveness for an AI agent.

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