Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

GetIncidentService

Retrieve detailed information about an incident service, including related users if specified, using the incident service ID. Integrates with Datadog MCP Server for enhanced observability and incident management.

Instructions

Get details of an incident service. If the include[users] query parameter is provided, the included attribute will contain the users related to these incident services.

Path Parameters:

  • service_id (Required): The ID of the incident service.

Query Parameters:

  • include: Specifies which types of related objects should be included in the response.

Responses:

  • 200 (Success): OK

    • Content-Type: application/json

    • Response Properties:

      • included: Included objects from relationships.

    • 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"
  ]
}
  • 401: Unauthorized

    • 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
includeNoObject related to an incident.
service_idYesThe ID of the incident service.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
includedNoIncluded objects from relationships.
Behavior2/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 describes the tool as a read operation ('Get details'), which implies it's non-destructive, but doesn't mention authentication requirements, rate limits, or error handling beyond the listed HTTP responses. The description includes response examples, but these are generic (e.g., 'unknown_type'), adding little practical value. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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, repetitive HTTP response details (e.g., multiple error examples with identical content) that don't add meaningful guidance. The core purpose is buried among unnecessary technical specifications, making it inefficient and hard to parse quickly. Sentences like 'If the `include[users]` query parameter is provided...' are useful but lost in the clutter.

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 moderate complexity (2 parameters, no annotations, but with an output schema), the description is partially complete. It covers the basic purpose and parameters but lacks usage guidelines and detailed behavioral context. The output schema exists, so the description doesn't need to explain return values, but it still falls short in providing a holistic understanding for an AI agent, especially without annotations to fill 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?

The schema description coverage is 100%, with clear descriptions for both parameters. The description adds minimal value beyond the schema: it repeats that 'service_id' is required and mentions 'include' can fetch related users, but the schema already documents the enum values ('users', 'attachments'). Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't significantly enhance parameter understanding.

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 details of an incident service.' It specifies the verb ('Get') and resource ('incident service'), making the action explicit. However, it doesn't differentiate from sibling tools like 'GetIncident' or 'ListIncidentServices,' which would require a 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 mentions an optional 'include' parameter for related objects but doesn't explain when to use this tool over other incident-related tools like 'GetIncident' or 'ListIncidentServices.' No explicit when/when-not or alternative recommendations are provided.

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