Skip to main content
Glama
Sign In
MCP Datadog Server

MCP Datadog Server

by micaelmalta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_event_details

Retrieve complete details for a specific Datadog event by its ID. Access timestamps, comments, and metadata to understand event context.

Instructions

Get detailed information about a specific event. Returns full event data including timestamps, comments, 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": {
      "eventId": "<eventId>"
    },
    "name": "get_event_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdYesUnique identifier of the event to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Without annotations, the description carries the transparency burden. It discloses the return content (timestamps, comments, metadata) but does not explicitly confirm read-only nature or handle edge cases. However, the verb 'Get' implies a read operation, and the simplicity mitigates the gap.

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?

Two sentences, front-loaded, no redundant information. Efficient.

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?

For a simple single-parameter get tool, the description adequately explains the purpose and return value. It mentions key output fields, but lacks explicit error/not-found behavior. Given its low complexity, this is sufficiently complete.

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 provides full coverage for eventId with a clear description. The tool description does not add additional parameter semantics, so baseline 3 applies.

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 retrieves detailed information for a specific event, using a specific verb and resource. It distinguishes from list/search tools by implying singular retrieval, though it doesn't explicitly name alternatives.

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?

Usage is implied rather than explicit. It suggests using when full event details are needed for a known event ID, but doesn't provide when-not conditions or alternatives.

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

Deploy Server

Other Tools