Skip to main content
Glama
Sign In
omni-dev

omni-dev

by rust-works
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

datadog_downtime_list

List Datadog scheduled downtimes to identify monitor muting windows. Optionally filter to currently active ones for quick status checks.

Instructions

List Datadog scheduled downtimes (monitor muting windows). active_only (boolean, optional, default false) restricts to currently-active downtimes; omit or set false to include past and future ones. Read-only. Mirrors omni-dev datadog downtime list. Output is YAML.

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

Input Schema

NameRequiredDescriptionDefault
active_onlyNoWhen `true`, restricts results to currently-active downtimes. Defaults to `false` (include past and future downtimes too). Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.33.0
    • removedInput schema / description
      Removed value: -"Parameters for the `datadog_downtime_list` tool."
    • removedInput schema / title
      Removed value: -"DatadogDowntimeListParams"
  2. Changed1 schema field changedv0.31.0
    • changedInput schema / properties / active_only / description
      Previous value: -"When true, restricts results to currently-active downtimes."New value: +"When `true`, restricts results to currently-active downtimes.\nDefaults to `false` (include past and future downtimes too).\nOptional."
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The description declares the tool is read-only and mentions output format (YAML). With no annotations, this provides basic behavioral insight but lacks detail on pagination, rate limits, or side effects.

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 two sentences, highly concise, front-loaded with purpose, and contains no extraneous information.

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 the tool's simplicity (one optional parameter, no output schema), the description adequately covers purpose, parameter behavior, read-only nature, and output format. It is complete for its complexity level.

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 sole parameter 'active_only' is thoroughly described in both the description and schema. The description explains its effect and default value, adding value beyond 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 tool lists scheduled downtimes (monitor muting windows) and specifies the key parameter. While it does not explicitly differentiate from sibling tools, the name and description make its purpose clear.

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 mentions the active_only parameter and its default behavior but does not provide guidance on when to use this tool over alternatives. No exclusions or when-not-to-use advice is given.

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