MCP server for JSONOTE - a JSON-based note-taking application with GitHub and local storage support
Three tools with basic schemas and descriptions in Korean. All tools have input schemas with type definitions and descriptions present. However, descriptions are minimal (10-30 chars in English translation), parameter descriptions lack actionable detail, and output schemas are not documented. No error handling guidance, no pagination support for list_notes, and no idempotency hints for create_note. The server lacks composition patterns, no batch operations, no natural-language identifier support (read_note requires exact id or title match), and no recovery guidance on errors.
새로운 노트를 작성합니다.
제이소노트의 모든 노트 목록을 가져옵니다.
특정 ID 또는 제목의 노트 내용을 읽습니다.
Descriptions are too brief (10-30 chars) and lack actionable context. 'Get all notes list' does not explain when to call this vs read_note, what structure is returned, or pagination behavior.
Output schemas are not documented. Callers cannot know what fields list_notes returns (only id, title, updatedAt?) or what structure create_note returns. LLMs must guess downstream field names.
read_note accepts both 'id' and 'title' but neither is marked required. Ambiguous which takes precedence if both provided. No guidance on mutual exclusivity or fallback behavior.
Error handling is minimal. read_note returns isError=true with plain text '노트를 찾을 수 없습니다.' (note not found) but does not suggest alternatives or recovery steps. No guidance for LLM on what to do next.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
create_note has no idempotency hint or confirmation step. Agents retrying on ambiguous failures risk duplicate notes. No dry-run or confirmation_required pattern.