NarrativeNode MCP server has critical definition quality gaps. Tool definitions lack proper input schemas for most tools, descriptions are present but inconsistent in depth, and parameter documentation is sparse. Only 2 of 9 tools have visible parameter schemas (get_tool_help, add_entity_to_scene). Most tools lack structured output schema documentation. Error handling and recovery guidance are absent. The server appears to proxy write operations through a session/token model (request_mcp_session, then use token with write tools), but this is not clearly documented in tool descriptions. Read-only tools have basic descriptions but lack specificity about return structure and fields. Write tools (create_scene, add_participants, set_entity_awareness) lack complete parameter documentation and output schema clarity.

• Define complete JSON Schema input schemas for all 9 tools. For write tools (create_scene, add_participants, set_entity_awareness), specify required parameters, types, and constraints. Example: create_scene should document parameters like 'scene_name' (string, required, max 256 chars), 'scene_description' (string, optional), 'participants' (array of entity IDs, optional).
• Document output schemas for each tool. Use JSON Schema in tool definitions to specify response structure. Example: get_project_summary should return {entities: [{id, name, description}], scenes: [{id, name, description}], relationships: [...], total_count: number}.
• Clarify session/token flow in tool descriptions. Explicitly state: 'First call request_mcp_session to obtain an activation_token. Pass this token in the Authorization header or as a session_token parameter to write tools. Write tools verify the token is active before executing.'
• Add parameter descriptions to all tools that currently lack them. For each parameter, provide: what it controls, valid format, constraints (length, enum, regex), and examples. Example for add_participants: 'participant_relationships (array of objects, required): List of {from_entity_id, to_entity_id, relationship_type} tuples. Relationship types: ally, enemy, mentor, rival.'
• Add error recovery guidance to tool descriptions. For each write tool, document: 'On failure, returns error_code and error_message. If error_code is 'conflict', the resource already exists, call get_project_summary to verify. If error_code is 'unauthorized', your session token expired, call request_mcp_session again.'