Loading ToolBench
Universal AI Developer & Agent Memory Engine (MCP Server with Sub-Millisecond Search & RAM Virtual Mapped SQLite)
CortexDB has well-structured tool definitions with complete schemas and descriptions for all 7 tools. Naming follows verb_noun convention (remember, search, store, get, delete, optimize). Descriptions are substantive (100-250 chars), explaining WHAT and WHEN. However, output schemas are not documented, LLMs cannot predict response structure. Parameter descriptions are good but lack format constraints (e.g., no regex for tags, no min/max for limit). Error handling and recovery guidance are absent from tool descriptions. Security considerations (e.g., file path traversal risks in projectPath) are not addressed. Composition is sound, tools are single-responsibility and chainable via IDs.
Permanently deletes an outdated, deprecated, or incorrect memory record or shared code pattern from SQLite storage and the active search index using its unique numeric database ID.
Retrieves stored code patterns from the central cross-project library matching the given name or description terms.
Inspects active workspace repository to detect project context, returning its tech stack, recent architectural decisions, and active global rules.
Performs deep SQLite storage optimization by executing disk defragmentation (VACUUM), B-Tree statistics analysis (ANALYZE), and WAL checkpoint truncation.
Creates a brand new memory record OR performs an in-place update on an existing record (if numeric id is provided). Records architectural decisions, bug fixes, rules, or learned lessons scoped to the current project or as an organizational GLOBAL rule.
Searches the high-speed SQLite FTS5 index in sub-milliseconds to find relevant past decisions, architectural patterns, and bug resolutions.
Output schemas not documented. LLMs cannot predict response structure (fields, types, pagination). Tools return results but descriptions omit what fields to expect.
Parameter constraints missing. 'limit' has no min/max (baseline: 1 - 100). 'tags' has no length/format guidance. 'projectPath' accepts arbitrary strings, no validation against path traversal.
No error recovery guidance. Tool descriptions do not explain what to do if a call fails (e.g., 'If project not found, try cortex_get_project_summary first'). No categorization of errors as retryable vs fatal.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 67 | 2026-07-28+ | v2 |
Stores or updates a reusable, high-quality code template (snippet/pattern) into the centralized cross-project developer pattern library.
Destructive operations lack confirmation step. cortex_delete_record and cortex_optimize_database (VACUUM) are irreversible but have no dry-run or confirmation mechanism.
Security: projectPath parameter accepts arbitrary file system paths. No validation against directory traversal or access control. Tool descriptions do not mention permission requirements or audit logging.