Skip to main content
Glama

server_doctor

Read-onlyIdempotent

Perform proactive server health analysis, detecting disk trending full, high swap, stale packages, and other issues. Returns severity-grouped findings with remediation commands.

Instructions

Run proactive health analysis on a server. Detects disk trending full, high swap, stale packages, elevated fail2ban bans, audit regression streaks, old backups, and reclaimable Docker space. Uses cached metrics by default — pass fresh=true to fetch live data via SSH. Returns findings grouped by severity (critical/warning/info) with remediation commands. For a full scored security audit across 27 categories, use server_audit instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverNoServer name or IP. Auto-selected if only one server exists.
freshNoFetch live data via SSH instead of using cached metrics. Default: false (reads cache only).
formatNoOutput format: summary (grouped findings with counts), json (full DoctorResult).summary
autoFixNoRun diagnose->fix chain automatically. Default: false (read-only).
dryRunNoShow what fixes would be applied without executing SSH. Requires autoFix: true.
forceNoSkip per-finding confirmation prompts (CI-safe). Requires autoFix: true.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true and destructiveHint=false, but the description mentions 'Run diagnose->fix chain automatically' via autoFix parameter, which implies mutation. This is a direct contradiction. Description does not clarify or reconcile this inconsistency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is concise (4 sentences), front-loaded with the tool's primary purpose, and includes necessary details without fluff. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (6 parameters, enum, output schema exists), the description covers all needed context: purpose, function, output grouping, and alternative tool. It is complete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All parameters are fully described in the input schema (100% coverage). The description adds minimal additional semantics beyond the schema (e.g., caching behavior), but does not provide deeper meaning for individual parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool's purpose ('Run proactive health analysis on a server') and lists specific health categories (disk trending, high swap, etc.). It explicitly distinguishes from the sibling 'server_audit' tool, providing a precise scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear guidance on when to use the tool (proactive health checks) and when not (for full security audit, use server_audit). Also explains optional parameters like fresh and autoFix to control behavior.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kastelldev/kastell'

If you have feedback or need assistance with the MCP directory API, please join our Discord server