Skip to main content
Glama
Render MCP Server

Render MCP Server

by meiti-dev

render_compare

Compare two app versions before and after a change on desktop and phone, checking the home page and up to three linked pages to flag visual regressions, missing interactions, or broken pages.

Instructions

Compare two versions of the same app (for example before and after a change): the home page and up to 3 pages it links to, on a phone and a desktop. Says WORSE if a visual issue appears, an interactive element disappears or a page stops opening; BETTER if issues were fixed; SAME otherwise.

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_before": "<url_before>",
      "url_after": "<url_after>"
    },
    "name": "render_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
url_afterYes
url_beforeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the crawl breadth (home page plus up to 3 links), the two viewports tested, and the exact verdict semantics including what triggers WORSE (visual regression, disappearing interactive element, page failing to open) versus BETTER. It omits operational behavior such as expected runtime, whether both URLs must be reachable apps, and any auth requirements, which is the remaining gap.

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?

Two sentences, zero waste, and front-loaded: the comparison scope comes first, the outcome semantics second. The second sentence is long but every clause (WORSE criteria, BETTER, SAME) carries distinct decision-relevant information.

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

Completeness4/5

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

For a tool with no annotations, no output schema, and two undocumented parameters, the definition covers the most important unknown - what the return verdicts mean and how they are derived - which is unusually strong. It falls short of a 5 only because operational facts about a multi-page, multi-viewport render (cost, time, failure modes) are absent.

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 0% for both parameters, so the description must compensate. It does clarify the intent of the pair (two versions of the same app, ordered before/after) via the 'before and after a change' framing, but it never states that the values are URLs, whether they must be same-origin, or what happens if the two differ structurally.

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?

The description names a specific verb (compare) and a specific resource (two versions of the same app), then bounds it precisely: the home page plus up to 3 linked pages, on phone and desktop. That level of scope detail makes it trivially distinguishable from siblings like render_open or render_scan, which read as single-page or single-action tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied through the parenthetical '(for example before and after a change)', which gives a concrete scenario but never states when to prefer this over render_scan or render_expect. No exclusions, prerequisites, or alternative-selection guidance are offered, so the agent must infer the fit from the purpose statement alone.

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