Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

GetCostByOrg

Retrieve monthly cost data across multi-organization accounts in Datadog. Use start_month and optional end_month parameters to query historical costs, available by the 16th of the following month. Accessible for parent-level organizations.

Instructions

Get cost across multi-org account. Cost by org data for a given month becomes available no later than the 16th of the following month. Note: This endpoint has been deprecated. Please use the new endpoint /historical_cost instead.

This endpoint is only accessible for parent-level organizations.

Query Parameters:

  • start_month (Required): Datetime in ISO-8601 format, UTC, precise to month: [YYYY-MM] for cost beginning this month.

  • end_month: Datetime in ISO-8601 format, UTC, precise to month: [YYYY-MM] for cost ending this month.

Responses:

  • 200 (Success): OK

    • Content-Type: application/json;datetime-format=rfc3339

    • Response Properties:

      • data: Response containing Chargeback Summary.

    • Example:

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

    • Content-Type: application/json;datetime-format=rfc3339

    • Response Properties:

      • errors: A list of errors.

    • Example:

{
  "errors": [
    "Bad Request"
  ]
}
  • 403: Forbidden - User is not authorized

    • Content-Type: application/json;datetime-format=rfc3339

    • Response Properties:

      • errors: A list of errors.

    • Example:

{
  "errors": [
    "Bad Request"
  ]
}
  • 429: Too many requests

    • Content-Type: application/json;datetime-format=rfc3339

    • Response Properties:

      • errors: A list of errors.

    • Example:

{
  "errors": [
    "Bad Request"
  ]
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_monthNoDatetime in ISO-8601 format, UTC, precise to month: `[YYYY-MM]` for cost ending this month.
start_monthYesDatetime in ISO-8601 format, UTC, precise to month: `[YYYY-MM]` for cost beginning this month.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoResponse containing Chargeback Summary.
Behavior4/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 effectively adds context beyond what the input schema provides: it explains data availability timing (cost data available by the 16th of the following month), deprecation status, access restrictions (parent-level organizations only), and includes detailed HTTP response codes (200, 400, 403, 429) with examples. This provides good behavioral transparency for a read operation.

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 for an MCP tool definition. It includes extensive HTTP response documentation that belongs in API documentation rather than an MCP description. The core purpose is buried among deprecation warnings, access notes, and response examples. While some information is valuable, the presentation isn't front-loaded or efficiently organized for an AI agent.

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 (cost reporting with timing constraints), the description provides substantial context: deprecation status, access restrictions, data availability timing, and parameter details. With an output schema present (implied by the response documentation), the description doesn't need to explain return values. However, the inclusion of full HTTP response documentation makes it more complete than necessary for an MCP context.

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 (start_month, end_month) fully documented in the schema. The description repeats this parameter information in the 'Query Parameters' section but doesn't add significant meaning beyond what's already in the schema descriptions. This meets the baseline of 3 for high schema coverage.

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 as 'Get cost across multi-org account' and 'Cost by org data for a given month', which specifies the verb (get), resource (cost), and scope (multi-org, by month). However, it doesn't explicitly differentiate from sibling tools like 'GetEstimatedCostByOrg' or 'GetHistoricalCostByOrg', leaving some ambiguity about when to choose between them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides some usage context: it notes that the endpoint is deprecated and recommends using '/historical_cost' instead, and specifies it's only accessible for parent-level organizations. However, it doesn't explicitly state when to use this tool versus alternatives like 'GetEstimatedCostByOrg' or 'GetHistoricalCostByOrg' from the sibling list, nor does it provide clear when-not-to-use guidance beyond the deprecation warning.

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