Nervous System
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_frameworkA | Get the complete Nervous System governance framework with all 7 rules |
| get_nervous_system_infoB | Get system info, version, and production stats |
| check_preflightC | Check if a file is protected (UNTOUCHABLE) |
| get_origin_storyB | Get the origin story of The Nervous System |
| get_handoff_templateB | Get a session handoff template |
| get_worklog_formatB | Get the worklog entry format |
| get_step_back_promptC | Get a step-back reflection prompt |
| get_dispatch_templateB | Get a task file template for dispatching agents |
| emergency_kill_switchA | Emergency stop all agents (requires KILL_SECRET env var) |
| verify_audit_chainB | Verify the tamper-evident SHA-256 audit trail |
| dispatch_to_llmB | Dispatch a task to a background Claude Code agent |
| audit_mcp_configA | Governance lint for MCP server configurations (free, local). Checks: plaintext secrets in env, unpinned packages, auto-install flags, broad filesystem scopes, shell wrappers, non-TLS remote transports, unpinned docker tags. Returns findings with severities and a 0-100 score. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Governance Rules | All 7 Nervous System rules |
| Production Stats | Live production statistics |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose. The 'get_*' tools all retrieve different templates or info, and the action-oriented tools (audit, check, dispatch, kill, verify) are easily distinguishable from each other. There is no overlap or ambiguity.
Most tools follow a verb_noun pattern (e.g., audit_mcp_config, get_dispatch_template). However, a few exceptions like 'dispatch_to_llm' (includes preposition) and 'emergency_kill_switch' (adjective-noun) break the pattern slightly, making it mostly consistent with minor deviations.
With 12 tools, the set is well-scoped for a governance/agent management system. Each tool addresses a specific need: configuration auditing, file protection, agent dispatch/stop, template retrieval, system info, and audit verification. No tool seems unnecessary or overly niche.
The tool set covers core governance, auditing, and agent dispatching well. Notable minor gaps include the lack of a tool to list running agents or check agent status, which might be expected in a system that dispatches agents. However, the existing tools cover the primary workflows.