Skip to main content
Glama

Compare Designs

compare_designs

Compare two design images to identify similarities, differences, a verdict, and the top five changes needed to match a reference or differentiate from it.

Instructions

Compare two design images: what is the same, what differs, a verdict, and the top 5 changes to either match the first design or differentiate from it.

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": {
      "image_a": "<image_a>",
      "image_b": "<image_b>"
    },
    "name": "compare_designs"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNomatch
image_aYesPath or URL of design A (the reference)
image_bYesPath or URL of design B

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the return contents (verdict, top-5 changes). However, it omits whether this is read-only, what image formats/paths are accepted, whether large images are a constraint, and how the comparison handles the reference role of image A beyond the schema note.

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?

A single front-loaded sentence that lists the four output components in a logical order with zero wasted words. It reads cleanly and immediately conveys scope.

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 3-parameter comparison tool with no output schema or annotations, the description covers purpose, the goal semantics, and the shape of results. Minor gaps remain around image constraints and read-only safety, but nothing essential to invoking it correctly is missing.

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

Parameters4/5

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

The schema covers image_a/image_b paths and the goal enum, and the description adds real meaning to goal by explaining the outcome of each value (make B match A, or make it distinct). It does not explain what happens if image_a and image_b are the same or the accepted URL forms, but overall it enhances the structured data.

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 resource ('two design images') and enumerates the exact outputs: same, differs, verdict, top 5 changes. This differentiates it from analyze_design or critique_design, which operate on one design, without needing to name them.

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 goal distinction (match the first design vs. differentiate from it) implicitly conveys the two use cases and which is the reference, but there is no explicit when-to-use/when-not guidance versus sibling tools like analyze_design or originality_check. The usage context is implied rather than stated.

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