rush

by jamesdsizemore

Overview Schema Source Related Servers Discussions Admin

Python

Local

rush_mutation

Import a local mutation report or run mutation testing to uncover untested code paths and strengthen test coverage.

Instructions

Import a local mutation report or run mutation testing under --allow-slow.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes
`options`	Yes
`allow_slow`	No
`test_paths`	No
`allow_build`	No
`report_path`	No
`source_paths`	No
`allow_browser`	No
`allow_network`	No
`allow_download`	No
`timeout_seconds`	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.

Changed4 schema fields changedv0.2.2Sep 15, 2026

addedInput schema / properties / source_paths

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Source Paths"
+}

addedInput schema / properties / test_paths

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Test Paths"
+}

addedInput schema / properties / timeout_seconds

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Timeout Seconds"
+}

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?

Annotations are absent, so the description carries the full burden. It only mentions two actions but does not disclose side effects, permission requirements, or what the allow_* flags control. It does not state whether running mutation testing modifies files, requires network access, or what happens on import. This is a significant gap for a tool with 13 parameters implying varied behaviors.

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

Conciseness3/5

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

The description is a single concise sentence, which is appropriate in length. However, it lacks any structure or elaboration; it is under-specified rather than efficiently concise, omitting essential context needed for correct usage.

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?

With 13 parameters, two distinct modes, and an output schema present but not described, the description is grossly incomplete. The agent cannot determine which parameters apply to importing vs. running, what the output format is, or how flags like allow_build or allow_network affect behavior. This is far from sufficient for a tool of this complexity.

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%, so the description must explain the parameters. It only references '--allow-slow' indirectly, leaving the other 12 parameters completely undocumented. The description adds no semantic value to the schema fields, making it nearly impossible for an agent to correctly populate options.

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 clearly states it can 'Import a local mutation report or run mutation testing', specifying a clear verb and resource (mutation testing). However, it does not differentiate from siblings like rush_test or rush_coverage; an agent might not know when mutation testing is preferred over those.

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?

There is no guidance on when to use this tool versus alternatives. No mention of when importing is preferable over running, nor any exclusions or prerequisites. The agent is left to infer usage context entirely.

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

Deploy Server