Connects Claude (or any MCP client) to Kitsu production management via the Gazu API.
Server has 6 tools with basic schemas and descriptions. All tools have names starting with action verbs (list_, get_, update_) and descriptions present. However, descriptions are generic (avg ~80 chars, below the 194-char baseline for A+ tools). Parameter descriptions exist but are minimal. No output schemas documented. Error handling returns dicts but lacks recovery guidance. The update_asset tool accepts a generic 'data' object without schema constraints. No tool annotations (readOnlyHint/destructiveHint) despite clear risk distinctions (5 READ_ONLY, 1 WRITE). Missing pagination support on list_assets despite potential for large result sets.
Get full details of an asset including its tasks and statuses.
Get an overview of a project: team, task types, asset types, and task status summary.
Get task statistics for a project grouped by status.
List assets in a project, optionally filtered by asset type.
List all open productions/projects in Kitsu.
Update an asset's description or custom metadata.
update_asset accepts untyped 'data' object parameter with no schema constraints or description of valid keys. LLMs cannot infer what metadata fields are allowed.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., project_id, asset_id) for chaining.
No tool annotations (readOnlyHint/destructiveHint) despite clear risk profile: 5 READ_ONLY tools and 1 WRITE tool. Agents cannot distinguish safe from destructive operations.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 66 | <=2025-11-25 | v2 |
list_assets lacks pagination (limit, offset, page_size). Large projects could return hundreds of assets, exhausting context window. No total count or next_cursor returned.
Error responses return bare dicts (e.g., {'error': 'Project not found'}) without recovery guidance. LLMs cannot determine next steps (retry, lookup alternatives, ask user).