system-status

Purpose

Get comprehensive system information

Description

The system-status tool returns detailed information about the server's operational state, including memory usage, system load, and service health. This is useful for monitoring resource utilization, diagnosing performance issues, and understanding the overall health of the deployment.

Unlike the simple healthcheck tool, system-status provides in-depth metrics about:

• Memory usage (used vs available)
• CPU load averages (1, 5, and 15 minute intervals)
• Service availability (Redis, database, etc.)
• Overall operational status

Parameters

None - this tool requires no input parameters.

Example Usage

Ask Claude:

"What's the system status?"
"Show me the current resource usage"
"Check memory and CPU load"
"Are all services running?"

Response

**System Status**
Status: operational
Memory: 45% used (2.1GB / 4.0GB)
Load: 0.8, 0.6, 0.5 (1m, 5m, 15m)
Services: Redis ✓, Database ✓

The response includes:

Status

• operational: All systems functioning normally
• degraded: Some services experiencing issues
• critical: Major systems are down or failing

Memory

• Percentage used: Current memory utilization
• Used / Total: Absolute memory values (e.g., 2.1GB / 4.0GB)

Load Average

Three numbers representing system load over different time periods:

• 1m: Average load over the last 1 minute
• 5m: Average load over the last 5 minutes
• 15m: Average load over the last 15 minutes

Lower numbers indicate less system stress. Values above the number of CPU cores may indicate performance issues.

Services

Health status of critical services:

• ✓ (checkmark) = Service is healthy and responding
• ✗ (cross) = Service is down or not responding

Authentication

Required: No

The system-status endpoint is publicly accessible and does not require authentication. This allows monitoring systems to track server health without credentials.

Common Use Cases

Performance Monitoring

"What's the current memory usage?"
"Show me the CPU load over the last 15 minutes"

Capacity Planning

"Are we approaching memory limits?"
"What's the average system load?"

Troubleshooting

"Why is the server slow? Check the system status"
"Are all services healthy?"

Service Verification

"Is Redis connected and responding?"
"Check that the database is available"

Understanding Load Averages

Load average represents the average number of processes waiting for CPU time:

• < 1.0: System has available capacity
• 1.0: System is fully utilized but not overloaded
• > 1.0: System is overloaded with more work than it can handle

For a server with 2 CPU cores:

• Load of 0.5 means 25% utilization
• Load of 1.0 means 50% utilization
• Load of 2.0 means 100% utilization
• Load of 4.0 means 200% utilization (overloaded)

Related Tools

• healthcheck - Quick health check without detailed metrics
• echo - Test basic connectivity
• user-info - Check authentication status

Next Steps

• All Tools - Return to tools overview
• Architecture - Learn about the server architecture