Skip to main content
Glama
Sign In
Datadog MCP Server

Datadog MCP Server

by dreamiurg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-incidents

Retrieve Datadog incidents with severity, status, commander, and timeline to manage and analyze incidents by query or time range.

Instructions

List Datadog incidents for incident management. Use for 'show active incidents', 'what incidents happened this week', or 'find incidents related to payments'. Includes severity, status, commander, and timeline.

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": "get-incidents"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageSizeNo
pageOffsetNo
queryNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so description bears full burden. It only states 'List' (read operation) and mentions included fields, but omits pagination, rate limits, authentication requirements, or any limitations.

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?

Three sentences, front-loaded with purpose, no redundant information. Efficient and structured for quick comprehension.

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?

Despite moderate complexity (4 params, no annotations, no output schema), description lacks detail on return format, pagination behavior, filtering semantics, and sibling tool distinctions. Incomplete for an agent to use correctly without external knowledge.

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

Parameters2/5

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

Schema description coverage is 0%. Description does not explain parameters like pageSize, pageOffset, or limit. Example usage for query is implicit but not explained. Provides minimal added meaning beyond schema.

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?

Clear verb+resource: 'List Datadog incidents for incident management.' Provides specific example use cases that distinguish it from other incident-related tools like get_incident_services or get_incident_timeline.

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?

Gives example phrases like 'show active incidents', but does not contrast with sibling tools such as search_incidents or other listing tools. Usage guidance is implied but not explicit about when to choose this over alternatives.

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