Skip to main content
Glama

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "files": "<files>"
    },
    "name": "review_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
viaNoSet 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.
filesYesThe 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
contextNoShort label for this review, e.g. the feature or branch name

Output Schema

NameRequiredDescriptionDefault
scoreYes0-100; confirmed criticals cap it — one at 59, two at 49, three or more at 39
issuesYes
summaryYes
directionNoWhat the change is trying to be — judgment before findings
visualPairNoOne verified before/after of the top fix (image URLs), when one was rendered
reviewsUsedYes
reviewsLimitYesnull = unlimited (Team overage applies instead)
detectedCountsYes
visualFindingsNoFindings seen in a render of the code, each with a crop URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / files / items / additionalProperties
      Removed value: -false
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / visualFindings / items / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / visualPair / additionalProperties
      Previous value: -trueNew value: +{}
  2. Changed3 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
    • addedOutput schema / properties / visualFindings
      Added value: +{
      +  "description": "Findings seen in a render of the code, each with a crop URL",
      +  "items": {
      +    "additionalProperties": true,
      +    "properties": {},
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / visualPair
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "One verified before/after of the top fix (image URLs), when one was rendered",
      +  "properties": {},
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • 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"
  4. Changed1 schema field changed
    • 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"
      +}
  5. Changed1 schema field changed
    • 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"
  6. Changed1 schema field changed
    • 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"
      +}
  7. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare a non-readonly, non-destructive, non-idempotent operation; the description goes well beyond them by disclosing credit consumption per call, the permission threshold for small reviews, and the consent requirement for large audits. The scoring cap rules and issue payload (severity, category, file:line, patches) further quantify what the agent gets back.

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

Conciseness5/5

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

Front-loads the purpose and return contract, then moves to when-to-call, then cost/permission rules and the alternative. Sentences are dense but each carries actionable information, with no filler or restatement of the tool name.

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?

For a billed, multi-file review tool with an output schema and full annotation coverage, the description covers everything the agent needs to decide and invoke: supported inputs, size limits implied by the audit rule, cost, consent, and the sibling alternative. Return values are correctly left to the output schema.

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 schema already documents files, path/content, via, and context. The description repeats the pasted-code path convention (pasted/Card.tsx) that is already in the schema and says nothing extra about the via or context parameters, which leaves it at the baseline rather than adding meaning.

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 and resource ("Full Rams design review of UI code"), enumerates the supported frameworks, and describes the output shape (0-100 score with severity caps plus file:line fixes). It names quick_review as the lightweight counterpart, so an agent can distinguish the two 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 explicit timing ("Call it once at the end: before a commit, or when the user wants a score or a final check"), an explicit alternative for the opposite case ("For quick feedback while you work, use quick_review"), and a scope boundary requiring user consent for whole-codebase audits.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources