A Model Context Protocol server for Datadog API integration
13 tools with consistent naming (verb_noun pattern: query, search, list, get) and basic descriptions. However, descriptions are generic and lack LLM-optimization guidance. Parameter schemas are present but descriptions are minimal (10-30 chars typical). No output schemas documented. Error handling is basic (generic error messages). Missing parameter constraints (enums, ranges, formats). No indication of idempotency, destructiveness, or permission requirements. Composition is reasonable (single responsibility per tool), but chaining metadata (IDs needed for follow-up calls) is not explicitly documented in responses.
Get a specific dashboard by ID
List all dashboards
Query events with start, end timestamps and optional filters for priority, sources, and tags
List hosts with optional filtering by filter, from, sort_field, sort_dir, start, and count
Aggregate logs with query, from, to, and aggregation parameters
Search logs in Datadog with query, from, to, and optional limit parameters
Get timeseries data for logs with query, from, to, and aggregation parameters
No output schemas documented. LLMs cannot plan downstream tool calls or extract required fields (e.g., IDs for chaining). Datadog API responses are verbose; no evidence of stripping irrelevant metadata or capping result limits.
Parameter descriptions are too brief (10-30 chars). 'Filter by tags (optional)' does not explain format, constraints, or examples. LLMs cannot infer whether to pass 'env:prod,service:api' or 'env=prod&service=api' or a JSON array.
No enum constraints on string parameters. 'sort_dir' accepts 'asc' or 'desc' but is defined as free-form string. LLMs may hallucinate 'ascending', 'ASC', or 'up'. Enums are self-documenting and prevent invalid values.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | <=2025-11-25 | v2 |
Query Datadog metrics with a given query string, from and to timestamps
Get a specific monitor by ID
List all monitors with optional filtering by tags, monitor_tags, page, and page_size
Search RUM (Real User Monitoring) events with query, from, to, and optional limit parameters
List services from the service catalog with optional pagination and environment filtering
Search spans with query, from, to, and optional limit, cursor, and sort parameters
No pagination guidance in tool descriptions. Tools like datadog_logs_search and datadog_spans_search accept 'limit' but do not state default, max, or whether results are truncated. LLMs may request 1000 items and exhaust context.
Error handling is generic. Router returns 'Error: {e}' with no recovery guidance. LLMs cannot distinguish retryable (rate limit, timeout) from user-fixable (invalid query) from fatal (auth failure) errors.