Skip to main content
Glama

nightward_status

Checks the boundary verdict of the last regression run without executing tests, revealing intact, breached, partial, incomplete, stale, or unknown status; rerun after code edits for a fresh result.

Instructions

Read the boundary signal of the LAST nightward_run, without running tests.

It does not see code edits made since that run: after changing code, call
nightward_run for a fresh verdict. Same shape as nightward_run (diffs
included), without warnings. boundary is "intact" (done), "breached" (unapproved changes),
"partial" (approved behaviors not checked: their test was deselected),
"incomplete" (capture tests failed or errored; see incomplete), "stale"
(the baseline, capture or rejections moved since that run, so its verdict can't be
trusted: run again) or "unknown" (no report yet). generated_at says when
the run happened; store names the store read (dir: omit it, as for
nightward_run).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nightward_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and it does well: it discloses staleness behavior, why a 'stale' verdict cannot be trusted, that no warnings are emitted, and that diffs are included. It omits permissions, or the cost of what it reads from disk, but the behavioral contract is mostly covered.

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

Conciseness4/5

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

The core distinction is front-loaded in the first sentence, and the long list of boundary states has a purpose. The parenthetical asides make it dense, but no sentence is wasted.

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

Completeness4/5

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

There is no output schema and no annotations, so the description supplies the return shape itself: 'boundary', 'generated_at', 'store', diffs, and the separate 'incomplete' field. It is nearly sufficient for calling the tool correctly, with the only gap being the unresolved meaning of 'dir'.

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?

Schema coverage is 0% for the single 'dir' parameter, so the description should compensate. It only says 'store names the store read (dir: omit it, as for nightward_run)', which delegates the meaning of 'dir' to another tool rather than explaining it, so it only partly compensates.

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?

It states a specific verb (read), a specific resource (the boundary signal of the LAST nightward_run), and a scope caveat (without running tests). It is also explicitly distinguished from the sibling nightward_run, so an agent can tell the two apart without opening schemas.

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?

It names its alternative and the condition that selects it: 'after changing code, call nightward_run for a fresh verdict.' It also states what this tool cannot see (code edits since the run), which is a practical exclusion.

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

Deploy Server

Other Tools