sovseal MCP server exposes 2 tools with basic schemas and descriptions. Naming follows verb_noun convention (store_memory, recall_memory), which is good. However, descriptions are sparse (12 - 17 words each), parameter documentation is minimal, output schemas are not documented, and error handling guidance is absent. The server lacks the LLM-optimized detail expected of production tools. Tool definitions are visible in source and properly registered, but quality falls in the D/C boundary due to incomplete parameter guidance and missing recovery instructions.

• Expand store_memory description to ~100 - 150 chars: 'Embed text content and write to the local LanceDB store. Writes are asynchronous and replicated server-side (if configured with an API key). Content is searchable via recall_memory immediately after the call returns. Use this to persist user context, decisions, or observations for later retrieval. Maximum content length: 100KB.'
• Expand recall_memory description to ~120 chars: 'Perform semantic search over stored memories using L2 distance. Returns the top-K most similar memories by embedding distance. Use this after store_memory to check what has been saved, or to retrieve context relevant to the current task.'
• Add explicit output schema documentation in the tool definition (e.g., via a 'responseSchema' field or comments): store_memory returns {success: boolean, memoryId: string, replicationStatus: 'queued'|'synced'|'error'}; recall_memory returns {hits: Array<{id, content, similarity}>}.
• Add bounds and format constraints to recall_memory.topK: 'Number of results to return. Must be between 1 and 100. Default: 5.' This prevents abuse and sets LLM expectations.
• Add length/format constraints to store_memory.content: 'Text content to embed and store. Must be valid UTF-8, non-empty, and less than 100KB. Longer content will be truncated or rejected with an error.'
• Document error cases and recovery paths: 'If store_memory fails due to LanceDB errors, the server returns {success: false, error: 'string description'}. Retry after a short delay. If recall_memory returns zero hits, try with a broader or rephrased query.'