Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

GetIncidentIntegration

Retrieve metadata details for incident integrations by providing incident and metadata UUIDs. Enables efficient management and analysis of integration data within Datadog's observability platform.

Instructions

Get incident integration metadata details.

Path Parameters:

  • incident_id (Required): The UUID of the incident.

  • integration_metadata_id (Required): The UUID of the incident integration metadata.

Responses:

  • 200 (Success): OK

    • Content-Type: application/json

    • Response Properties:

      • included: Included related resources 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"
  ]
}
  • 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
incident_idYesThe UUID of the incident.
integration_metadata_idYesThe UUID of the incident integration metadata.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
includedNoIncluded related resources that the user requested.
Behavior2/5

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

No annotations are provided, so the description carries full burden. While it includes HTTP response codes and examples, it doesn't disclose important behavioral traits: authentication requirements, rate limits, whether this is a read-only operation, or what happens with invalid UUIDs beyond generic error codes. The response examples show 'unknown_type' for data fields, which provides minimal practical guidance about return structure.

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 poorly structured with excessive HTTP response documentation that belongs in an API reference rather than an agent tool description. The core purpose is buried under technical details. While the initial sentence is concise, the bulk of the text (error codes, examples, content types) doesn't help an agent understand when and how to use the tool effectively.

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 2 parameters with 100% schema coverage and an output schema exists, the description is minimally adequate. However, for a tool with no annotations, it should provide more behavioral context about authentication, error handling specifics, and practical usage. The HTTP response documentation adds bulk without adding meaningful agent guidance about tool behavior.

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?

Schema description coverage is 100%, with both parameters clearly documented in the schema. The description repeats the parameter information verbatim from the schema ('The UUID of the incident' and 'The UUID of the incident integration metadata'), adding no additional semantic context about format expectations, where to find these IDs, or relationships between them. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Get incident integration metadata details' which is a clear verb+resource combination, but it's somewhat vague about what 'metadata details' specifically entail. It doesn't distinguish this tool from sibling tools like 'GetIncident' or 'ListIncidentIntegrations' - the agent would need to infer this retrieves specific metadata for a particular integration rather than general incident data or a list of integrations.

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?

No guidance is provided about when to use this tool versus alternatives. The agent must deduce from the name and parameters that this retrieves metadata for a specific integration within a specific incident, but there's no explicit comparison to sibling tools like 'GetIncident' (general incident data) or 'ListIncidentIntegrations' (list of integrations). No prerequisites or context for usage is mentioned.

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