MCP server for analyzing Docker container logs, identifying error patterns, and providing incident summaries with root cause analysis and recommended actions.
Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output structure. get_container_logs has a clear purpose and acceptable defaults, but summarize_incident lacks output schema documentation. Neither tool documents return types or error recovery guidance. Parameter descriptions are minimal (e.g., 'Number of log lines to retrieve' lacks format/range constraints). No tool annotations (readOnlyHint, idempotentHint) despite both being read-only operations. Error handling returns plain strings rather than structured objects, making it hard for LLMs to parse failures and decide next steps.
Read the last N lines of logs from a specific Docker container.
Summarize recurring log issues and suggest likely next actions.
Output schemas not documented. Both tools return plain strings; LLMs cannot parse structured results or extract fields for downstream tool calls.
Parameter descriptions lack format/range constraints. 'lines' parameter has no min/max bounds; LLMs could pass 0, negative, or absurdly large values.
Error responses are unstructured strings with no recovery guidance. 'Failed to read logs from container' gives LLM no actionable next step.
No tool annotations despite both tools being read-only. Missing readOnlyHint and idempotentHint metadata.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | 2026-07-28+ | v2 |
summarize_incident description is vague about output format. Does it return JSON, plain text, or structured incident data? LLMs cannot plan downstream actions.