Skip to main content
Glama
LunenLabs

nightward

Official
by LunenLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nightward_status

Reads the boundary signal from the last test run without re-running tests. Shows whether behavior is intact, breached, partial, incomplete, stale, or unknown after code changes.

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, 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).

Input Schema

NameRequiredDescriptionDefault
dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well. It discloses that the tool is a read operation, does not run tests, does not see subsequent code edits, and explains each boundary state including stale and unknown verdicts.

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 main purpose and sibling distinction are front-loaded, and the detailed boundary-state explanations earn their place because there is no output schema. The description is somewhat dense with parentheticals and could be structured more cleanly, but it is not padded.

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?

Given the absence of annotations and an output schema, the description does substantial work by explaining boundary values, generated_at, store, and the stale/incomplete conditions. It still leans on 'same shape as nightward_run' for some return details, but the core semantics an agent needs to call and interpret the tool are present.

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?

There is one optional parameter, dir, and schema description coverage is 0%. The description adds partial guidance by saying 'dir: omit it, as for nightward_run,' but it does not explain what dir means when supplied or what value to use, so it compensates only partially for the schema gap.

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?

The description states a specific verb and resource: 'Read the boundary signal of the LAST nightward_run.' It also distinguishes this tool from its sibling by saying it works 'without running tests,' so an agent can tell it apart from nightward_run without opening either schema.

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?

The description gives explicit usage guidance: read this tool for the last run's signal, but after changing code 'call nightward_run for a fresh verdict.' It also explains that this tool does not see edits made since that run, which directly tells the agent when not to rely on it.

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