No user-submitted related servers found.
Scored across 7 tools
Each tool targets a distinct resource or action: HTTP requests, git status, database queries, project discovery, process listing, port listing, and log reading. There is no functional overlap; even similar tools like list_processes and list_ports focus on different aspects of system state. The descriptions further clarify boundaries, ensuring an agent can confidently select the right tool.
All tool names use snake_case and are clear, but there is a mix of noun-phrase names (http_request, git_status, db_query) and verb-noun names (inspect_project, list_processes, list_ports, read_logs). While the style is consistent, the lack of a uniform verb-noun pattern is a minor deviation from ideal consistency, though it remains readable and predictable.
With 7 tools, the server is well-scoped for a runtime diagnostic purpose. Each tool covers a distinct aspect of investigation—project config, processes, ports, logs, git state, database queries, and HTTP probing—without redundancy or bloat. The count feels appropriate for the domain and does not overwhelm or underdeliver.
The tool surface covers the core diagnostic lifecycle: initial project discovery (inspect_project), environment inspection (list_processes, list_ports), historical context (read_logs, git_status), data exploration (db_query), and direct endpoint testing (http_request). There are no obvious dead ends—agents can fully investigate runtime issues using these tools together. The read-only nature aligns with the intended purpose, and optional write capabilities (e.g., POST via http_request) are available when explicitly enabled.