Mitosis Docs

Agent readability score

Strengths

• Tool names use consistent 'cortex_' prefix with clear functional intent
• Descriptions provide detailed use cases for memory management operations
• Some tools explicitly state preference hierarchy (e.g., cortex_ask over cortex_recall)

Weaknesses

• Several descriptions are incomplete or abruptly cut off
• Parameter schemas and required/optional fields are not documented
• Potential overlap between cortex_ask and search tools creates ambiguity

• cortex_manifest — Description cuts off mid-sentence, missing critical details about source indexing
• cortex_connectable_sources — Incomplete description truncates explanation of data connection issues
• search — Shares similar memory search functionality with cortex_ask without clear differentiation
• cortex_remember — No explicit error handling for invalid source_universal_ids parameter
• fetch — Lacks clarification on error responses for invalid item ids

Verdict

The toolset demonstrates strong conceptual organization with clear naming conventions, but incomplete documentation and functional overlaps reduce usability. Parameter definitions and error handling need standardization across tools to improve agent reliability.

9/11/2026, 6:15:05 AM

Event narrative

Server transitioned to legacy era with compliance score improvement from null to 100.

Risk: medium

• 2026-09-10T21:16:35.016Z — era changed from auth-gated to legacy · transition to legacy era with no compliance data
• 2026-09-11T05:44:28.819Z — complianceScore increased from null to 100 · achieved full compliance in legacy era

Advice

Monitor complianceScore trends and investigate why smokeOk remains null despite high compliance. Ensure legacy era configurations are properly validated.