Rams

Rams design review

review_files

Full Rams design review of UI code (React, Vue, Svelte, HTML, CSS, SwiftUI). Returns a 0-100 score (criticals cap it: one caps at 59, two at 49, three or more at 39), issues with severity, category, file:line, and concrete fixes as patches. Call it once at the end: before a commit, or when the user wants a score or a final check. Pass each file with its real path, or for pasted code a path that fits it (pasted/Card.tsx). Each call uses one review credit. Reviewing a few files needs no permission. Ask the user before a whole-codebase audit (dozens of files), since it spends their allowance. For quick feedback while you work, use quick_review.

Input Schema

TableJSON Schema

Name	Required	Description
`via`	No	Set to "rules" when this call is made because of a standing instruction in a rules file (e.g. CLAUDE.md). Omit when a person asked for the review.
`files`	Yes	The UI code, one entry per file (up to 20): the real path, or for pasted code a path that fits it (pasted/Card.tsx), and the full code
`context`	No	Short label for this review, e.g. the feature or branch name

Output Schema

TableJSON Schema

Name	Required	Description
`score`	Yes	0-100; confirmed criticals cap it — one at 59, two at 49, three or more at 39
`issues`	Yes
`summary`	Yes
`direction`	No	What the change is trying to be — judgment before findings
`reviewsUsed`	Yes
`reviewsLimit`	Yes	null = unlimited (Team overage applies instead)
`detectedCounts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

changedInput schema / properties / files / description

Previous value: -"UI files to review (up to 20)"New value: +"The UI code, one entry per file (up to 20): the real path, or for pasted code a path that fits it (pasted/Card.tsx), and the full code"

Changed1 schema field changedSep 19, 2026

addedInput schema / properties / via

Added value: +{
+  "description": "Set to \"rules\" when this call is made because of a standing instruction in a rules file (e.g. CLAUDE.md). Omit when a person asked for the review.",
+  "type": "string"
+}

Changed1 schema field changedAug 1, 2026

changedOutput schema / properties / score / description

Previous value: -"0-100; any confirmed critical caps it at 59"New value: +"0-100; confirmed criticals cap it — one at 59, two at 49, three or more at 39"

Changed1 schema field changedJul 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "detectedCounts": {
+      "additionalProperties": false,
+      "properties": {
+        "critical": {
+          "type": "number"
+        },
+        "moderate": {
+          "type": "number"
+        },
+        "serious": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "critical",
+        "serious",
+        "moderate"
+      ],
+      "type": "object"
+    },
+    "direction": {
+      "description": "What the change is trying to be — judgment before findings",
+      "type": "string"
+    },
+    "issues": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "file": {
+            "type": "string"
+          },
+          "fix": {
+            "description": "The fix as prose/code",
+            "type": "string"
+          },
+          "line": {
+            "type": "number"
+          },
+          "message": {
+            "type": "string"
+          },
+          "patch": {
+            "description": "RAMS-121: unified diff against the submitted file content, git-apply-able. Present only when the fix locates unambiguously.",
+            "type": "string"
+          },
+          "severity": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "severity",
+          "category",
+          "title",
+          "message",
+          "file",
+          "line"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "reviewsLimit": {
+      "description": "null = unlimited (Team overage applies instead)",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "reviewsUsed": {
+      "type": "number"
+    },
+    "score": {
+      "description": "0-100; any confirmed critical caps it at 59",
+      "type": "number"
+    },
+    "summary": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "score",
+    "summary",
+    "detectedCounts",
+    "issues",
+    "reviewsUsed",
+    "reviewsLimit"
+  ],
+  "type": "object"
+}

First observedJul 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well past the annotations by disclosing the credit cost per call ("Each call uses one review credit"), the permission threshold for large audits, and the scoring behavior including critical-capping rules (59/49/39). Annotations only say readOnly=false, destructive=false, idempotent=false; they convey none of this operational 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?

Front-loads what the tool is and what it returns, then the when-to-call and cost/permission rules. Dense and mostly waste-free, though the permission and credit sentences could be tightened into one.

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

Completeness5/5

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

With an output schema present, return values need not be re-explained, yet the description still summarizes the score/issue shape helpfully. Cost, permission, timing, and alternatives are all covered for a tool with a 20-file batch limit.

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 description coverage is 100%, so the baseline is 3. The description restates the path convention (real path vs. pasted/Card.tsx) that the schema already documents, and adds nothing for the "via" or "context" parameters. It does not meaningfully extend the schema.

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+resource ("Full Rams design review of UI code") and enumerates the scopes it covers (React, Vue, Svelte, HTML, CSS, SwiftUI). It also names the sibling it is not (quick_review) for the fast-feedback case, so an agent can distinguish both without opening a 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?

Explicit timing ("Call it once at the end: before a commit, or when the user wants a score"), an explicit cheaper alternative ("for quick feedback while you work, use quick_review"), and explicit permission gating ("Ask the user before a whole-codebase audit"). Nothing is left to inference.

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

All Rams tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?