Overview
Tool Name
Purpose
The system_manager_tools group centralizes platform administration. Generate chat titles automatically, check overall health, toggle maintenance mode, adjust configuration, perform safe cleanups, and restart components when required. All operations are routed through a single entrypoint for predictable governance.Key Features & Functions
Auto-Title Conversations
Generate concise chat titles that reflect conversation context.
Health & Status
Retrieve real-time system status with optional connectivity checks.
Maintenance Control
Enable or disable maintenance mode with messages and timing.
Configuration Management
Get, set, update, or reset system configuration keys safely.
Cleanup Operations
Remove temporary files, old logs, or expired sessions with dry-run support.
Targeted Restarts
Restart the platform or specific components with explicit confirmation.
Audit & Logging
Keep an administrative trail of system actions and outcomes.
Input Parameters for Each Function
All operations usemanage_system with an action value.
AUTO_TITLE_CHAT
Parameters
| Name | Definition | Format |
|---|---|---|
| conversation_id | Conversation to generate a title for. | String |
| conversation_content | Optional summary to guide title quality. | String |
| title_length | Max title length. | Integer |
SYSTEM_STATUS
Parameters
| Name | Definition | Format |
|---|---|---|
| include_details | Include component level details. | Boolean |
| check_connectivity | Run connectivity probes where available. | Boolean |
MAINTENANCE_MODE
Parameters
| Name | Definition | Format |
|---|---|---|
| enable | Turn maintenance mode on or off. | Boolean |
| maintenance_message | Optional banner message for users. | String |
| estimated_duration | Estimated duration in minutes. | Integer |
SYSTEM_CONFIG
Parameters
| Name | Definition | Format |
|---|---|---|
| config_operation | One of GET, SET, UPDATE, RESET. | String |
| config_key | Configuration key to read or modify. | String |
| config_value | New value when setting or updating. | String |
CLEANUP_TASKS
Parameters
| Name | Definition | Format |
|---|---|---|
| cleanup_type | One of temporary_files, old_logs, expired_sessions, all. | String |
| retention_days | Keep newer items for this many days. | Integer |
| dry_run | Preview what would be removed without deleting. | Boolean |
SYSTEM_RESTART
Parameters
| Name | Definition | Format |
|---|---|---|
| component | Optional component name to restart. | String |
| force_restart | Skip graceful shutdown if true. | Boolean |
| confirmation | Must be true to proceed. | Boolean |
Use Cases
- Generate descriptive chat titles for better search and navigation.
- Monitor platform health, component readiness, and external connectivity.
- Schedule maintenance windows with user-facing messages and durations.
- Adjust configuration keys safely and audit the changes.
- Reclaim space by cleaning temporary files, old logs, or expired sessions.
- Restart a misbehaving component after validating dependencies.
- Maintain an administrative trail of system actions for compliance.
Workflow/How It Works
- Assess current health with
SYSTEM_STATUSand decide on next steps. - Communicate by enabling
MAINTENANCE_MODEwith a clear message and duration. - Change settings via
SYSTEM_CONFIGto apply the desired configuration. - Clean using
CLEANUP_TASKSwithdry_run = true, then execute for real. - Restart selected components using
SYSTEM_RESTARTwith explicit confirmation. - Verify recovery with
SYSTEM_STATUSand disable maintenance mode.
Prefer
dry_run for cleanups and staged config updates to reduce risk in production.Integration Relevance
- genesis_job_tools to coordinate or pause background jobs during maintenance.
- system_stats_tools for performance verification before and after changes.
- make_baby_bot to manage data agent availability during platform updates.
- harvester_tools to align metadata crawls with maintenance windows.
- All tools that rely on system configuration or uptime benefit from predictable scheduling.
Configuration Details
- Use precise
config_keynames and document them in your runbook. - Maintenance messages should be concise and include a contact or status page.
- Choose conservative
retention_daysto avoid premature log or session removal. - Component names for restarts should match deployed service identifiers.
- Auto-title works best with a short, representative
conversation_contentwhen available.
Limitations or Notes
- Administrative privileges are required for all actions.
- Maintenance mode affects all users, so schedule during low activity periods.
- Some configuration changes may require a restart to take effect.
- Cleanups are destructive unless you have separate backups.
- Status checks can have overhead during peak load.
- Cross-component dependencies may delay restarts or require ordering.
Output
- Auto-Title: Proposed title, relevance score, and suggested alternatives.
- Status: Overall health plus component details and connectivity results.
- Maintenance: Mode status, banner message, and timing confirmation.
- Configuration: Current values, change confirmations, and diffs where applicable.
- Cleanup: Dry-run preview or executed results with counts and recovered space.
- Restart: Acknowledgment, component recovery status, and timing.
- Errors: Actionable messages for permission issues, invalid keys, or failed operations.