Skip to main content
Glama
Sign In
MCP Image Compare Server

MCP Image Compare Server

by leky90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

compare_urls

Capture screenshots of two webpages and compare them pixel by pixel. Returns difference statistics and a diff image showing visual changes.

Instructions

Compare screenshots from two different URLs. Captures screenshots of both webpages and compares them pixel by pixel. Returns difference statistics and a diff image showing the visual differences.

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": {
      "url1": "<url1>",
      "url2": "<url2>"
    },
    "name": "compare_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
url1YesURL of the first webpage to capture
url2YesURL of the second webpage to capture
includeAANoOptional: If true, include anti-aliased pixels in the diff. Default: false
thresholdNoOptional: Matching threshold (0-1). Lower values are more sensitive. Default: 0.1
diff_output_pathNoOptional: Path where the diff image will be saved. If not provided, a timestamped file will be created.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries full disclosure burden. It mentions capturing screenshots and pixel-by-pixel comparison, but does not address potential issues like dynamic content, network timeouts, or resolution behavior.

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 convey purpose and output clearly. No unnecessary words, highly efficient.

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 5-parameter tool with no output schema, the description explains the return type (difference statistics and diff image) sufficiently. However, it could be more specific about the statistics format (e.g., percentage difference) given the lack of 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 coverage is 100%, so baseline is 3. The description adds high-level context but does not elaborate on parameter semantics beyond what the schema already provides. The threshold and includeAA parameters are adequately described in 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?

The description explicitly states the verb 'compare' and resource 'screenshots from two URLs' and distinguishes from sibling tools (compare_images, compare_image_with_url) by specifying that it works with URLs, not pre-captured images.

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?

The description implies when to use the tool (comparing two webpages), but does not provide when-not-to-use or highlight alternatives. With sibling tools available, explicit guidance would improve clarity.

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

Deploy Server

Other Tools