Skip to main content
Glama
po4erk91

Thread Keeper

by po4erk91
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

shadow_review_status

Read-only

Check shadow-review daemon health with its config, recent passes, and 24h/7d production telemetry; verify outcome mix, evaluator hit rates, and skill writes.

Instructions

Show shadow-review config, recent passes, and production telemetry.

Snapshot for sanity-checking that the daemon is alive and advancing its cursor, PLUS the production-validation rollup (issue #6): for the 24h and 7d windows it aggregates how often the daemon fired, the outcome mix (no_window / too_short / spawned / deferred / error), the MATERIALIZED-vs-SKIP hit rate of spawned evaluator children, durable skill writes attributable to shadow_review, and the total Claude-spawn time spent — so you can tell whether the loop earns its Opus minutes or just emits SKIPs.

Use shadow_review_snapshot(snapshot_path) to write a markdown report; this read-only status call never writes it.

Input Schema

NameRequiredDescriptionDefault
snapshot_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.0
    • addedInput schema / properties / snapshot_path
      Added value: +{
+  "default": "",
+  "title": "Snapshot Path",
+  "type": "string"
+}
  2. First observedv0.13.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces it while adding context annotations cannot carry: it clarifies that despite accepting a snapshot_path, this call never writes it. It also enumerates the returned telemetry (outcome mix, MATERIALIZED-vs-SKIP hit rate, spawn time), which is genuine behavioral detail. Missing only auth/rate-limit context.

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?

Purpose is front-loaded in the first sentence, and every clause about the telemetry rollup is informative rather than filler. The middle sentence is a dense run-on enumerating many outcome tokens, which slightly hurts readability.

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?

An output schema exists so return values needn't be detailed, yet the description still explains what is aggregated, which is helpful for a diagnostic tool. It covers the relationship to shadow_review_snapshot and the daemon-liveness purpose; only the snapshot_path parameter's own semantics remain unresolved.

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 optional snapshot_path param, so the description must compensate. It mentions snapshot_path but only in the context of the sibling tool, leaving it ambiguous why this tool exposes the parameter at all if it never writes it. Partial, not complete, compensation.

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?

States a specific verb (show) and resource (shadow-review config, recent passes, production telemetry), and explicitly distinguishes itself from the sibling shadow_review_snapshot, which writes a report. An agent can tell the two apart 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?

Gives a concrete use case ('sanity-checking that the daemon is alive and advancing its cursor') and names the alternative tool plus the condition that selects it ('use shadow_review_snapshot(snapshot_path) to write a markdown report; this read-only status call never writes it'). When, when-not, and alternative are all explicit.

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