Central Memory MCP demonstrates reasonable structure with 4 well-intentioned tools, but falls short of production-grade quality in several critical areas. All tools have descriptions and most have input schemas with type information, placing it in the 'Fair' range. However, parameter descriptions are inconsistent, output schemas are undocumented, error handling lacks actionable recovery guidance, and the use of both GUID-based and legacy name-based parameters creates ambiguous tool interfaces. The schema is visible and mostly typed, but several parameters lack descriptions entirely or have generic descriptions. The upsert_relation tool particularly suffers from confusing parameter naming (From/To vs FromEntityId/ToEntityId) and optional-vs-required ambiguity.

• Document the output schema for each tool. For example, read_graph returns {WorkspaceName, Entities: [], Relations: []}. For upsert_entity, return {success, id, workspace, name, entityType}. Include field types and descriptions so LLMs know what to expect.
• Refactor upsert_relation to use a single, clear parameter pattern. RECOMMENDED: Use only EntityId-based parameters (fromEntityId, toEntityId, both required or both optional but not mixed). Deprecate or remove the legacy From/To names. If supporting legacy names is necessary, add explicit documentation: 'Use fromEntityId and toEntityId (preferred). If unavailable, pass from and to entity names instead; they will be resolved at runtime.'
• Add pagination to read_graph and get_entity_relations. Accept optional limit (default 50, max 1000) and offset/cursor parameters. Return total_count or next_cursor so LLMs can page through results without blowing context.
• Standardize parameter naming: use camelCase consistently (workspaceName, entityId, entityName, relationType, fromEntityId, toEntityId). Remove inconsistency between function parameters and request classes.
• Enrich error messages with recovery guidance. Instead of 'Invalid entity payload', return 'Invalid entity payload: workspaceName, name, and entityType are required. Example: {"workspaceName": "my-workspace", "name": "Alice", "entityType": "Person"}' or 'Source entity "Bob" not found in workspace "my-workspace". Call get_entity_relations to list available entities first.'
• Add tool annotations (readOnlyHint, destructiveHint, idempotentHint) to clarify which operations are safe to retry. Mark read_graph and get_entity_relations with readOnlyHint=true. Mark upsert_entity and upsert_relation with idempotentHint=true (since they are 'upsert', not 'create').