Skip to main content
Glama

Rams page review

review_url

Review a live public web page by its URL, no code needed. Rams opens the page at desktop (1440px) and phone (390px) widths, measures the rendered page and looks at both screenshots, then returns the top design issues (severity, category, where on the page, and a fix in plain words) with a 0-100 score. Use it when the user names a site or a page: "review rams.ai with Rams", "how does my landing page look?". It takes up to a minute and uses one review credit. Public pages only: no sign-in pages, localhost or private addresses. It returns no code patches. If the user has the code for the page, use quick_review or review_files on those files instead.

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": {
      "url": "<url>"
    },
    "name": "review_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe page to review, e.g. https://rams.ai or rams.ai/pricing
focusNoOptional: what to put first, e.g. "mobile", "typography", "color"

Output Schema

NameRequiredDescriptionDefault
hostYesThe page that was reviewed (host only)
scoreYes0-100, what a designer sees in the two screenshots; one critical caps it at 59
scoresYes
summaryYes
findingsYesEvery finding, most severe first (the text shows the top 8)
reviewsUsedYes
reviewsLimitYesnull = unlimited
detectedCountsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / detectedCounts / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / findings / items / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / scores / additionalProperties
      Previous value: -trueNew value: +{}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "detectedCounts": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "critical": {
      +          "type": "number"
      +        },
      +        "moderate": {
      +          "type": "number"
      +        },
      +        "serious": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "critical",
      +        "serious",
      +        "moderate"
      +      ],
      +      "type": "object"
      +    },
      +    "findings": {
      +      "description": "Every finding, most severe first (the text shows the top 8)",
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "category": {
      +            "type": "string"
      +          },
      +          "fix": {
      +            "type": "string"
      +          },
      +          "instances": {
      +            "type": "number"
      +          },
      +          "measured": {
      +            "description": "true = measured on the rendered page, false = seen in the screenshot",
      +            "type": "boolean"
      +          },
      +          "message": {
      +            "type": "string"
      +          },
      +          "severity": {
      +            "description": "critical, serious or moderate",
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "viewport": {
      +            "description": "desktop or phone",
      +            "type": "string"
      +          },
      +          "where": {
      +            "description": "The element, when one element owns the finding",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "severity",
      +          "category",
      +          "viewport",
      +          "measured",
      +          "title",
      +          "message",
      +          "instances"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "host": {
      +      "description": "The page that was reviewed (host only)",
      +      "type": "string"
      +    },
      +    "reviewsLimit": {
      +      "description": "null = unlimited",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "reviewsUsed": {
      +      "type": "number"
      +    },
      +    "score": {
      +      "description": "0-100, what a designer sees in the two screenshots; one critical caps it at 59",
      +      "type": "number"
      +    },
      +    "scores": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "desktop": {
      +          "type": "number"
      +        },
      +        "phone": {
      +          "type": "number"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "summary": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "host",
      +    "score",
      +    "scores",
      +    "summary",
      +    "detectedCounts",
      +    "findings",
      +    "reviewsUsed",
      +    "reviewsLimit"
      +  ],
      +  "type": "object"
      +}
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld/idempotent/destructive flags; the description adds the operationally important facts an agent needs: the run takes up to a minute, consumes one review credit, works only on public pages, and returns no code patches. It also discloses the internal behavior (two viewport renders plus measurement) that explains the latency and credit cost.

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-loaded with the core action and mechanics, then triggers, then constraints and sibling routing — a sensible order. Slight redundancy between "no code needed" at the start and "It returns no code patches" near the end, but the density of useful information justifies the length.

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?

Even though an output schema exists and return values need not be described, the description still summarizes them usefully, and it covers cost, latency, access constraints, and alternatives. Nothing an agent needs in order to decide and call correctly is missing.

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 both url and focus, including the focus examples ("mobile", "typography", "color"). The description adds no additional meaning about the parameters themselves, only about the viewport defaults the tool applies, so the baseline of 3 applies.

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 ("Review a live public web page by its URL") plus the concrete mechanics: renders at 1440px and 390px, measures and screenshots the page, returns issues with severity/category/location/fix and a 0-100 score. This is unmistakably distinct from quick_review and review_files, which operate on code rather than a live URL.

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 an explicit trigger with example utterances ("review rams.ai with Rams", "how does my landing page look?"), explicit exclusions (no sign-in pages, localhost, private addresses), and an explicit routing rule to the siblings quick_review or review_files when the user has the code. Both when-to-use and when-not-to-use are covered.

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