Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

ListIncidentServices

Retrieve and filter incident services for your organization using query parameters like page size, offset, and name filters. Optionally include related users or attachments in the response.

Instructions

Get all incident services uploaded for the requesting user's organization. If the include[users] query parameter is provided, the included attribute will contain the users related to these incident services.

Query Parameters:

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

  • page[size]: Size for a given page. The maximum allowed value is 100.

  • page[offset]: Specific offset to use as the beginning of the returned page.

  • filter: A search query that filters services by name.

Responses:

  • 200 (Success): OK

    • Content-Type: application/json

    • Response Properties:

      • data: An array of incident services.

      • included: Included related resources which the user requested.

    • Example:

{
  "data": [
    {
      "id": "00000000-0000-0000-0000-000000000000",
      "type": "services"
    }
  ],
  "included": [
    "unknown_type"
  ],
  "meta": "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
filterNoA search query that filters services by name.
includeNoObject related to an incident.
page[offset]NoSpecific offset to use as the beginning of the returned page.
page[size]NoSize for a given page. The maximum allowed value is 100.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesAn array of incident services.
metaNo
includedNoIncluded related resources which the user requested.
Behavior3/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 describes pagination behavior ('page[size]', 'page[offset]'), filtering capabilities ('filter'), and inclusion options ('include'), which are useful. However, it lacks details on authentication requirements, rate limits (though error responses hint at 429), or whether the operation is read-only (implied by 'Get' but not explicit). The description adds value but misses key behavioral traits.

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 (status codes, examples) that are redundant with an output schema (which exists). The core purpose is buried among unnecessary technical specifications, making it less front-loaded and efficient. Sentences like the error response examples do not earn their place in a tool description.

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 context signals (4 parameters, 100% schema coverage, output schema exists), the description is reasonably complete. It explains the tool's purpose, parameters, and response behavior, and the output schema handles return values. However, it could improve by adding more behavioral context (e.g., authentication, rate limits) and clearer usage guidelines, but it's adequate for a list operation with good schema support.

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%, so the input schema already documents all parameters thoroughly. The description repeats some parameter details (e.g., 'filter' and 'include' explanations) but does not add significant meaning beyond the schema. It provides an example for 'include[users]' effect, which adds minor context. Baseline 3 is appropriate as the schema does the heavy lifting.

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 all incident services uploaded for the requesting user's organization.' It specifies the verb ('Get'), resource ('incident services'), and scope ('requesting user's organization'), making it easy to understand. However, it does not explicitly differentiate from sibling tools like 'GetIncidentService' or 'ListIncidents', which is why it doesn't achieve a perfect score.

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 minimal guidance on when to use this tool. It mentions that including 'users' adds related users to the response, but it does not specify when to use this tool versus alternatives like 'GetIncidentService' (for a single service) or 'SearchIncidents' (for broader searches). No explicit exclusions or prerequisites are stated, leaving usage context vague.

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