nightward
OfficialServer 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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nightward_runA | Run the tests, capture behaviors, and return the boundary signal. |
| nightward_statusA | Read the boundary signal of the LAST nightward_run, without running tests. |
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 2 tools
The two tools have clearly distinct purposes: nightward_run executes tests and produces a fresh boundary verdict, while nightward_status only reads the last run's report. The descriptions explicitly clarify the relationship and warn that status cannot see edits made after the last run. There is no meaningful overlap or risk of misselection.
Both tools share the consistent nightward_ prefix and snake_case formatting, making them clearly part of the same server. However, nightward_run uses a verb while nightward_status uses a noun, so the pattern is consistent in namespace but not strictly verb_noun throughout.
Two tools is on the thin side, but each is essential to the narrow agent-facing purpose: run the gate and read the most recent result. The server deliberately avoids duplicating human-only CLI operations, so the small surface is reasonable rather than excessive.
For the stated MCP purpose, the surface covers the full agent workflow: trigger a fresh test/gate run, then read the last boundary report without rerunning. Approval and review remain intentionally human-only CLI actions, so their absence is not a gap in this server's role.