rush

Overview Schema Source Related Servers Discussions Admin

rush_snapshot

Import or run snapshot tests with an optional accept flag to update stored snapshots; enable slow, build, browser, or network modes to validate output against recorded baselines.

Instructions

Import a local snapshot comparison or run snapshot tests under --allow-slow.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes
`accept`	No
`options`	Yes
`allow_slow`	No
`allow_build`	No
`report_path`	No
`allow_browser`	No
`allow_network`	No
`allow_download`	No
`allow_cache_write`	No
`allow_artifact_write`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`raw`	No
`tool`	No
`engine`	No
`status`	No
`metrics`	No
`summary`	No
`findings`	No
`metadata`	No
`artifacts`	No
`duration_ms`	No
`review_kind`	No
`engine_version`	No
`review_provider`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.2Sep 15, 2026

changedOutput schema / properties / metrics / anyOf

Previous value: -[
-  {
-    "additionalProperties": {
-      "anyOf": [
-        {
-          "type": "integer"
-        },
-        {
-          "type": "number"
-        },
-        {
-          "type": "string"
-        }
-      ]
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "number"
+        },
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv0.3.0Aug 30, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does not disclose whether snapshots are written, accepted, or compared only in memory, what the allow_* flags enable, or what side effects such as report_path or accept may cause.

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 description is short and front-loaded, avoiding redundancy. However, it is concise to the point of under-specification, so it earns credit for structure rather than completeness.

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

Completeness1/5

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

A tool with 11 parameters, no annotations, and no schema-level parameter descriptions needs far more context to be invoked correctly. The output schema covers return shape, but the description still omits mode semantics, flag meanings, and the effect of accept and report_path.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only mentions allow_slow without explaining it. It provides no meaning for the required path and options arguments, nor for accept, report_path, allow_build, allow_network, or the other flags.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states two concrete actions: importing a local snapshot comparison and running snapshot tests with the --allow-slow flag. This distinguishes it by resource type from many sibling tools, although 'local snapshot comparison' remains somewhat ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to call rush_snapshot versus related tools like rush_test, rush_visual, or rush_tui_diff. The mention of 'under --allow-slow' hints at a condition, but there are no explicit when-to-use instructions or exclusions.

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

Deploy Server