Skip to main content
Glama
ReftrixMCP
by TKMD

design.compare

Read-onlyIdempotent

Compare 2–5 web pages across layout, visual, quality, and color to get pairwise similarity scores; enable details to surface common patterns and key differences.

Instructions

2-5件のWebページをレイアウト・視覚・品質・カラーの4軸で比較し、ペアワイズ類似度スコア(0-1)を算出します。include_detailsで共通パターンと差分ポイントも取得可能。 / Compare 2-5 web pages across layout, visual, quality, and color dimensions. Returns pairwise similarity scores (0-1). Set include_details for common patterns and key 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": {
      "page_ids": "<page_ids>"
    },
    "name": "design.compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idsYes比較対象ページID(2-5件、UUID形式) / Page IDs to compare (2-5, UUID format)
dimensionsNo比較次元(デフォルト: 全4次元) / Comparison dimensions (default: all 4)
include_detailsNo共通パターン・差分ポイントを含めるか(デフォルト: false) / Include details (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.0
    • addedInput schema / properties / dimensions / maxItems
      Added value: +4
  2. Addedv0.3.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, so safety is covered; the description adds the output contract (pairwise scores normalized 0-1) and what include_details unlocks (common patterns and key differences). It does not mention cost/latency for a 2-5 page pairwise comparison, which is the main residual unknown.

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?

Each language block is two tight sentences, front-loaded with the action and scope, then the return value, then the optional flag. The bilingual duplication doubles the token footprint but is a consistent structural convention rather than filler.

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?

With no output schema, the description carries the burden of explaining returns and does so (pairwise similarity scores, optional detail block). Minor gap: it doesn't indicate output shape for N pages (e.g. number of pairs) or whether scores are per-dimension, which an agent assembling a report would want.

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 defines page_ids, dimensions, and include_details including defaults and bounds. The description restates the 2-5 range and clarifies that details mean common patterns and differences, but adds little beyond the existing field descriptions.

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?

Names a specific verb (compare) and a tightly scoped resource (2-5 web pages), plus the four comparison axes and the return (pairwise similarity 0-1). The 'web page' scope distinguishes it from siblings like part.compare, style.get_palette, or design.similar_site without needing the schemas.

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

Usage Guidelines4/5

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

Clearly signals the use case (multi-page comparison across layout/visual/quality/color) and tells the agent how to get extra output via include_details. It stops short of stating when NOT to use it or naming an alternative such as part.compare or quality.evaluate for single-page scoring.

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