Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

GetServiceDefinition

Retrieve a specific service definition from the Datadog Service Catalog by providing the service name and optional schema version. Supports structured JSON responses for accurate service data retrieval.

Instructions

Get a single service definition from the Datadog Service Catalog.

Path Parameters:

  • service_name (Required): The name of the service.

Query Parameters:

  • schema_version: The schema version desired in the response.

Responses:

  • 200 (Success): OK

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "data": "unknown_type"
}
  • 400: Bad Request

    • 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"
  ]
}
  • 409: Conflict

    • 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
schema_versionNoSchema versions
service_nameYesThe name of the service.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
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 includes HTTP response codes (e.g., 200, 400, 429) which hint at success, errors, and rate limits, but does not explicitly describe authentication needs, rate limiting behavior, or side effects. The mention of '429: Too many requests' implies rate limits but lacks details, leaving gaps in behavioral understanding.

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, with extensive HTTP response details that are redundant given the presence of an output schema. It includes repetitive error examples and formatting that does not efficiently convey essential information. The core purpose is buried under unnecessary technical documentation, reducing clarity and conciseness.

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 complexity (2 parameters, 100% schema coverage, output schema present), the description is mostly complete. It covers the purpose, parameters, and response codes, and the output schema handles return values. However, it lacks usage guidelines and detailed behavioral context, which slightly reduces completeness for agent decision-making.

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 both parameters ('service_name' and 'schema_version') well-documented in the input schema. The description repeats parameter names and types but adds minimal value beyond the schema, such as categorizing them as 'Path Parameters' and 'Query Parameters'. This meets the baseline for high schema coverage without significant enhancement.

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 a single service definition from the Datadog Service Catalog.' It specifies the verb ('Get') and resource ('service definition'), making the action explicit. However, it does not differentiate from sibling tools like 'ListServiceDefinitions' beyond the singular vs. plural naming, which is implied but not explicitly stated in the description.

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 does not mention sibling tools (e.g., 'ListServiceDefinitions' for multiple definitions) or any context-specific usage scenarios. The absence of such guidance leaves the agent without explicit direction for tool selection.

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