MCP server (stdio + Streamable HTTP) for basic-blog-convex-blog-cms: list/create/update posts via Convex.
Three tools with clear verb-noun naming (list_, create_, update_). All have descriptions and input schemas. However, descriptions are brief (avg 95 chars, below 194-char baseline), parameter descriptions are sparse or missing, and output schemas are not documented. The update_article tool has a complex nested patch object with many optional fields but lacks guidance on which combinations are valid or what the response structure is. No error handling guidance visible. Schemas are present but incomplete, many parameters lack descriptions, and no return types are specified.
Create a draft blog post (Convex post) with slug and title. Maps to createPost.
List blog posts (Convex posts) for admin, newest first. Maps to listPostsForAdmin.
Update a blog post (Convex post) by id. Maps to updatePost. Only include fields to change.
Output schemas not documented. LLMs cannot plan downstream calls or extract required fields (e.g., postId for chaining). list_articles, create_article, and update_article lack return type specifications.
Parameter descriptions missing or incomplete. 'limit' in list_articles has a description, but create_article's 'authorName' and 'excerpt' lack clarity on format/constraints. update_article's 'patch' object has 20+ nested fields with no per-field guidance on valid combinations or side effects.
No error handling guidance. Tools do not indicate what errors are retryable, user-fixable, or fatal. E.g., create_article with a duplicate slug will fail, but the error message and recovery path are not documented.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
Tool descriptions are brief (50 - 60 chars) and lack context on WHEN to use each tool or prerequisites. E.g., update_article does not explain that postId must come from list_articles or that status enum values are 'draft' and 'published'.
update_article's 'patch' parameter is an untyped object with 20+ optional properties. No schema constraints on which fields can be updated together, no guidance on immutable fields, and no documentation of side effects (e.g., does setting 'status' to 'published' auto-set 'publishedAt'?).