Memory Bank as a Service for collaborative AI agents. Provides tools for managing memory spaces, live notes, memory consolidation, backups, and admin functions with distributed S3 storage and LLM-powered consolidation.
No return/output schemas documented for any tool. Agents cannot infer what fields or structure to expect. Breaks tool chaining and forces agents to guess field names for downstream operations.
Document output schemas for ALL tools. Specify field names, types (string, number, array, object), and structure. Example: space_create should return {space_id: string, created_at: string, status: string}.
Expand all descriptions to 50-200 characters (baseline for A+ tools). Include: what the tool does, when to call it vs similar tools, prerequisites, and side effects. Example: 'Create a new memory space to organize notes by topic or project. Returns space_id for use in subsequent operations. Spaces are isolated and can be connected via graph edges.'
Add 'Confirmation Required' or 'Dry Run Supported' guidance to destructive tools. Example for space_delete: 'Permanently deletes a space and all its contents. No recovery is possible. Consider backup_create() before deletion or use backup_restore() to recover from backups.'
Add pagination parameters (limit, offset or cursor) to list tools (space_list, bank_list, graph_list, admin_list_tokens). Document default and maximum limits in descriptions.
Expand parameter descriptions to include: valid format/type, allowed values (enums if applicable), range/constraints, and dependencies. Example for space_id: 'Unique identifier for the space (alphanumeric, 2-64 chars, no spaces). Must be unique within the server.'
Document permission requirements for admin tools. Add to descriptions: 'Requires admin permission. Failure modes: InvalidToken (permission denied), SpaceNotFound. Retry on transient network errors only.'
For tools with similar names (space_*), add clarifying guidance in descriptions. Example: 'Use space_info to read properties, space_rules to view/set consolidation rules, space_rename to change the space ID.'
Destructive/admin tools (space_delete, bank_delete, backup_delete, backup_restore, admin_purge_tokens, admin_revoke_token) lack confirmation or dry-run support. Descriptions do not warn about irreversibility or provide recovery guidance. High risk of agent-initiated data loss.
Descriptions are uniformly terse (10-50 chars). They state WHAT the tool does but not WHEN to call it, WHEN to use vs a similar tool, or what prerequisites exist. Does not follow LLM-optimized description guidance (50-200 chars baseline for A+ tools).
Parameter descriptions exist but are minimal (e.g., 'ID of the space'). Do not explain valid formats, constraints, dependencies, or ranges. LLMs cannot infer whether to pass opaque IDs, names, or display identifiers.
No error handling guidance in tool descriptions. Tools do not document what failures are retryable, what needs user intervention, or what recovery steps exist. Agents cannot self-correct on failure.
List/read tools (space_list, bank_list, graph_list, admin_list_tokens) lack pagination parameters (limit, offset, cursor). Descriptions do not mention result caps. High risk of context window exhaustion on large datasets.
Parameter 'agent' in live_note and live_read, and 'client_name' in admin_create_token default to current token or inferred values. Descriptions do not clarify fallback behavior or when the parameter is required vs optional.
Tools operating on same resource (e.g., space_info, space_rename, space_delete, space_rules all on 'space') have similar names but unclear distinctions in descriptions. LLMs may conflate them or pick wrong variant.
bank_consolidate tool description does not explain what 'consolidate' means, what the LLM will do with the consolidated notes, or what format the output takes. Vague operation name and description.
bank_consolidate
Add error recovery guidance to all write/destructive tools. Example: 'On failure: check returned error code. Common errors: InvalidSpace (ID does not exist, call space_list to discover valid IDs), PermissionDenied (insufficient permissions, request admin role). Use backup_list to check if recovery is possible.'
Document constraints for bank_consolidate: what 'consolidate' means (e.g., AI-powered summarization of live notes into structured facts), how long it takes, and what format the consolidated output takes.
For optional parameters with defaults (e.g., 'agent' in live_note), clarify: 'If omitted, defaults to the agent name embedded in your authentication token. Pass explicitly to assign notes to a different agent.' Warn if this could cause confusion.
Add result caps and strip irrelevant fields from list/read operations. Example: space_list should return max 50 spaces by default and include only: space_id, description, created_at, note_count. Omit internal audit fields.
For backup_download, clarify output format: 'Returns tar.gz archive (base64 encoded). Decoding and extracting will restore directory structure /space_id/live/*, /space_id/bank/*, etc.'
Document admin_gc_notes action enum values and side effects. 'Action: scan (report orphaned notes), consolidate (merge into bank), or delete (remove). Consolidate and delete are irreversible, use backup_create first.'
Add tool annotations (readOnlyHint, destructiveHint, idempotentHint) in schema to mark operation intent and help clients present warnings to users.