MCP Datadog Server

get_log_details

Fetches complete details for a Datadog log entry by its ID, including all attributes and metadata.

Instructions

Get detailed information about a specific log entry. Returns full log data including all attributes and metadata.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "logId": "<logId>"
    },
    "name": "get_log_details"
  }
}

Input Schema

Name	Required	Description	Default
`logId`	Yes	Unique identifier of the log entry to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the return contents ('full log data including all attributes and metadata'), but does not mention error behavior, permissions, or any side effects (though 'get' implies read-only).

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

Conciseness5/5

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

The description is two concise sentences with no filler, front-loading the action and quickly conveying the purpose.

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 the small parameter count and lack of output schema or annotations, the description gives a high-level return description but omits details about return structure, error handling, or usage context. It is adequate but not comprehensive.

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 coverage is 100%—the schema already clearly documents logId as 'Unique identifier of the log entry to retrieve'. The description adds no parameter-specific meaning beyond what the schema provides.

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

Purpose5/5

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

The description uses the verb 'Get' with a specific resource 'log entry' and scope ('specific', 'full log data'), clearly distinguishing it from sibling search or aggregation tools. It is precise and actionable.

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 implies usage when a specific log ID is known and full details are needed, but it offers no explicit when-to-use/when-not-to-use guidance or references to alternative tools like search_logs or aggregate_logs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server