Skip to main content
Glama
Sign In
vision-bridge-mcp

vision-bridge-mcp

by G12789
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Compare two images

compare_images

Compare two images to identify differences between UI states or screenshots. Specify optional task for targeted analysis.

Instructions

Compare before/after screenshots or UI states. Absorbed pattern from image_mcp.

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": {
      "source_a": "<source_a>",
      "source_b": "<source_b>"
    },
    "name": "compare_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_aYes
source_bYes
taskNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the high-level purpose without detailing what the output looks like (e.g., diff image, boolean, text description), whether the operation is safe, or any side effects. The cryptic 'Absorbed pattern from image_mcp' adds no clarity.

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

Conciseness3/5

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

The description is short (two sentences), but the second sentence is vague and unhelpful. While concise, it lacks structure and misses important information like parameter details or output behavior.

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

Completeness1/5

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

Given no output schema, no annotations, and incomplete parameter documentation, the description fails to provide a complete understanding of the tool. The agent cannot determine what the tool returns, how the 'task' parameter affects behavior, or any prerequisites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not elaborate any parameter semantics. 'source_a' and 'source_b' are self-explanatory, but 'task' is left undefined. The description adds no value beyond the parameter names.

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 clearly states the tool compares images, specifically before/after screenshots or UI states, using a specific verb and resource. It distinguishes from sibling tools like describe_image, extract_text, etc., which serve different purposes.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives (e.g., describe_image for single image analysis). The description implies usage for comparison but does not provide context, exclusions, or when-not-to-use scenarios.

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