Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

ListLogsMetrics

Retrieve and manage log-based metrics configurations with their definitions using JSON responses. Streamline monitoring and observability on the Datadog platform.

Instructions

Get the list of configured log-based metrics with their definitions.

Responses:

  • 200 (Success): OK

    • Content-Type: application/json

    • Response Properties:

      • data: A list of log-based metric objects.

    • Example:

{
  "data": [
    "unknown_type"
  ]
}
  • 403: Not Authorized

    • 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

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoA list of log-based metric objects.
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 (200, 403, 429) with examples, which adds some context about success, authorization errors, and rate limiting. However, it lacks details on permissions required, pagination, sorting, or other operational behaviors that would help an agent use it effectively.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with a clear purpose statement, but it includes extensive HTTP response details that may be redundant if an output schema exists (which it does, per context signals). The response examples and properties add length without necessarily earning their place, as structured fields could handle this. It's somewhat verbose for a simple list operation.

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 that the tool has 0 parameters, 100% schema coverage, and an output schema exists, the description is adequate but not comprehensive. It covers the basic purpose and some error responses, but lacks usage guidelines and behavioral details like authentication needs or rate limit specifics. For a no-parameter tool, it's minimally viable but could be more helpful.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter information, which is appropriate here. A baseline of 4 is applied since there are no parameters to document, and the description doesn't introduce any confusion.

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 the list of configured log-based metrics with their definitions.' It uses a specific verb ('Get') and identifies the resource ('list of configured log-based metrics with their definitions'). However, it doesn't explicitly differentiate from sibling tools like 'GetLogsMetric' or 'ListLogsGet', which appear to be related but distinct operations.

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 doesn't mention any prerequisites, context for usage, or comparisons to sibling tools such as 'GetLogsMetric' or 'ListLogsGet'. The agent must infer usage based on the name and description alone.

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