Localhost Doctor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XAMPP_HOME | No | Set to the install root if your XAMPP/WAMP lives outside the standard folders (e.g., C:\xampp, C:\wamp64). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| diagnose_stackA | Full health check of the local XAMPP/WAMP stack: which stack processes are running, who owns ports 80/8080/443/3306, whether localhost answers HTTP, plus a verdict (healthy / degraded / port conflict) and concrete issues. |
| check_portC | Identify which process is listening on a TCP port (e.g. 80, 8080, 3306) and what that means for the local stack. |
| read_error_logsB | Read the tail of Apache/MySQL error logs from the detected install and explain error lines via the knowledge base. component: 'apache', 'mysql' or 'all'. |
| explain_symptomB | Explain a localhost symptom or error message. Paste the raw error text, e.g. 'localhost refused to connect' or 'MySQL shutdown unexpectedly'. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct primary angle (full diagnosis, single-port lookup, log reading, symptom explanation), so an agent can usually pick correctly. However, diagnose_stack already reports port ownership and verdicts, overlapping with check_port, and explain_symptom overlaps with read_error_logs' error-explanation role, creating mild risk of redundancy-driven misselection.
All four tools follow a clean verb_noun snake_case pattern: diagnose_stack, check_port, read_error_logs, explain_symptom. No deviations or mixed conventions.
Four tools is well-scoped for a local stack diagnostic helper, with each tool covering a recognizable facet of the problem space without bloat.
The surface covers diagnosis, port inspection, log reading, and symptom explanation, which matches the 'doctor' diagnostic purpose. Minor gap: no remediation tool (e.g., restart service or free a port) for when a conflict or degraded verdict is found, leaving agents to advise manually.