A Model Context Protocol server implementation in Java that provides tools for managing and retrieving presentation data
Single tool 'get_presentation' has critical definition gaps. Description is a placeholder ('description_for_presentation', 11 chars), fails the 20-char minimum and provides zero context for LLM selection. Input schema is present but lacks parameter descriptions entirely, the 'operation' string parameter has no guidance on valid values, format, or purpose. No output schema documented. Tool does not follow verb_noun naming (should be 'list_presentations' or 'get_presentations_by_operation'). No error handling, no pagination despite returning a list, no idempotency guidance. Baseline: 194 chars avg description, 72 chars avg param annotation, this tool has 0 and 0 respectively.
description_for_presentation
Tool description is a placeholder ('description_for_presentation', 11 chars). Fails 20-char minimum. LLM cannot determine when or why to select this tool.
Input parameter 'operation' has no description. LLM cannot infer what values are valid, what the parameter controls, or when to use it.
No output schema documented. LLM cannot plan downstream tool calls or extract structured data from results.
Tool returns a list but has no pagination (limit, offset, page_size) or result count. Large result sets will blow context window.
Tool name 'get_presentation' is ambiguous, does it fetch one, many, or filter by operation? Should be 'list_presentations' or 'get_presentations_by_operation'.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 25 | <=2025-11-25 | v2 |