rush

Overview Schema Source Related Servers Discussions Admin

rush_slop

Detect Python AI slop and deterministic JS/TS noise at a path. If sloppylint is missing and no fallback exists, returns status 'skipped'.

Instructions

Detect Python AI slop and deterministic JS/TS noise at ; missing sloppylint returns status='skipped' when no JS/TS fallback applies.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes

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

B3/5.0

Behavior3/5

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

No annotations are present, so the description carries the full burden. It discloses a specific edge case (missing 'sloppylint' leads to status='skipped' when no JS/TS fallback applies), which adds useful behavior. However, it does not state whether the operation is read-only, modifies anything, or requires permissions.

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 a single sentence with the main action front-loaded. The second half about 'sloppylint' is somewhat cryptic but does not add excessive length. It is concise and avoids redundancy.

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

Completeness3/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 are presumably covered there. The description explains one edge case but leaves ambiguities such as what 'sloppylint' is and whether the tool scans directories recursively. Given the tool's simplicity (one parameter), it is adequate but not fully comprehensive.

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

Parameters2/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 references the parameter as '<path>' without adding meaning beyond what the schema's 'path' format already implies. It does not clarify whether the path should be a file or directory, or what it should contain.

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 a specific verb ('Detect') and resource ('Python AI slop and deterministic JS/TS noise') at a given path. It is not a tautology and conveys a concrete function, though it does not explicitly differentiate from many sibling tools like rush_lint or rush_review.

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 use this tool versus alternatives. It does not mention prerequisites, typical use cases, or exclusions. The description only states the action and a behavioral caveat, leaving the agent to infer context.

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

Deploy Server