A Model Context Protocol (MCP) server for JSONPlaceholder API
Critical failures across all 6 tools. Descriptions are generic 10-word strings lacking context, parameter guidance, or LLM-optimized detail. No parameters are defined, typed, or described. Tools lack error recovery guidance, pagination support, and output structure documentation. No tool annotations (readOnlyHint, etc.). This server does not meet baseline production standards.
Fetch all albums from JSONPlaceholder API
Fetch all comments from JSONPlaceholder API
Fetch all photos from JSONPlaceholder API
Fetch all posts from JSONPlaceholder API
Fetch all todos from JSONPlaceholder API
Fetch all users from JSONPlaceholder API
All 6 tools have inputSchema: undefined and outputSchema: undefined.
Descriptions are 10-word generic strings ('Fetch all X from JSONPlaceholder API'). Under 20 chars minimum for actionable guidance. Missing WHEN to use, WHAT it returns, and error recovery hints.
No parameters defined for any tool. LLMs cannot filter, paginate, or customize results. JSONPlaceholder API supports query params (e.g. userId, _limit, _start) but tools expose none. Agents cannot request specific subsets.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 33 | 2025-06-18+ | v2 |
No pagination support. Handlers return all results (potentially 100+ items) without limit, offset, or cursor. Large responses blow context window and degrade LLM reasoning. Baseline: tools should cap results at 20-50 and offer pagination.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). All tools are read-only but this is not declared in the tool definition. Agents cannot infer safety properties.