Two tools identified: create_post (WRITE) and get_posts (READ_ONLY). Both have brief descriptions and basic input schemas visible in examples/wordpress-example.js, but several critical quality gaps reduce scores significantly. Naming follows verb_noun pattern (create_post, get_posts) which is good. However, descriptions are minimal (12-18 chars), parameter descriptions are generic/missing, output schemas are undocumented, and no error guidance is provided. The codebase shows HTTP transport and TypeScript/Express setup, but tool definitions are inferred from example file rather than directly visible in core tool registration code.

• Expand tool descriptions to 50-200 chars. Example: 'create_post: Creates a new WordPress post with title, content, and publication status. Returns post_id and post_url. Status draft saves unpublished; publish makes immediately visible.'
• Add per-parameter descriptions with constraints. Example for status: 'Publication status, draft (unpublished, editable), publish (immediately visible to readers), private (visible to logged-in users only).' Example for perPage: 'Posts per page, 1 - 100 (default 20).'
• Document output schemas in tool descriptions or via separate schema documentation. Example: 'Returns {post_id: string, post_url: string, status: string, title: string, created_at: ISO8601}' for create_post. 'Returns {posts: [{id, title, status, created_at, excerpt}], total: number, page: number, per_page: number}' for get_posts.
• Add error handling with recovery hints. Example: 'If status is invalid, must be one of: draft|publish|private. If content is empty, provide a non-empty string. If title exceeds 500 chars, truncate or split into multiple posts.'
• Implement pagination for get_posts. Add parameters: page (default 1), per_page (default 20, max 100). Return total_posts and has_next_page to let LLM know when to stop fetching.
• Locate and inspect actual tool handler code in src/server.ts or src/index.ts to verify tool registration uses proper MCP tool registration API with all schema and description fields populated.
• For create_post, add explicit side-effect language: 'Creates and optionally publishes a new post. This action is not reversible without calling delete_post or unpublish_post.'

Inferred effective spec: <=2025-11-25.

• Relies on Sampling (deprecated) - integrate directly with the LLM provider API