Three tools with basic schemas and descriptions, but significant gaps in description quality, parameter documentation, and error recovery guidance. All tools are read-only utility functions with minimal complexity. Descriptions are present but generic and lack LLM-optimization. No parameter descriptions exist for most tools. No output schemas documented. No error recovery hints. This is typical of early-stage personal-use servers that lack production-grade polish.
Returns a list of available file names starting with 'guide'
Lists all available prompt files in the PROMPT_DIR
Reads the content of a local file (text or image)
No parameter descriptions. All three tools have input schemas but parameters lack descriptions explaining format, constraints, or valid values. 'fileName' parameter in read_local_file has no description of accepted formats, path traversal protection, or file type constraints.
Tool descriptions lack LLM optimization. All three descriptions are under 100 chars and missing WHEN to use, WHAT the tool returns, and HOW it differs from related tools. List_prompts vs list_available_files distinction is unclear to an LLM.
No output schemas documented. LLM cannot predict response structure. Code returns {content: [{type: 'text', text: '...'}]} but this is not visible in tool definitions, LLM has no schema to guide downstream parsing.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 49 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 27 | - | v1 |
Error handling provides no recovery guidance. Read_local_file throws errors like 'Unsupported file type' and 'Unable to read file' but LLM gets no hints on what to do next (e.g., 'Try list_available_files to see supported files').
Path traversal risk in read_local_file. File parameter is resolved relative to a base path, but no documentation or validation prevents '../../../etc/passwd' style attacks. Tool uses path.resolve() which is safe, but LLM lacks guidance on valid input formats.
Missing parameter constraints. 'fileName' parameter has no maxLength, pattern, or enum. Code supports only .txt/.text extensions, but LLM cannot know this from the schema, will attempt to read unsupported types and fail.