Skip to main content
Glama
ReftrixMCP
by TKMD

part.compare

Read-onlyIdempotent

Compare 2-5 UI parts across styles, layout, interaction, and accessibility to determine property-level equality; defaults to styles and layout.

Instructions

2-5個のUIパーツをスタイル・レイアウト・インタラクション・アクセシビリティで並列比較。デフォルトはstyles+layout。各プロパティの同一性も判定。 / Compare 2-5 UI parts on styles, layout, interaction, and accessibility. Default: styles + layout. Reports property-level identity.

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": {
      "part_ids": "<part_ids>"
    },
    "name": "part.compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
part_idsYes比較対象パーツID(2-5個) / 2-5 part IDs to compare
compare_aspectsNo比較観点(デフォルト: styles, layout) / Aspects to compare (default: styles, layout)

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered by structured data. The description adds that comparison is property-level identity-aware and defaults to two aspects, but says nothing about error behavior for invalid/unknown part IDs or what a mismatch result looks like.

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?

Front-loaded with the operation and cardinality, then aspects and defaults — no wasted clauses. The Japanese/English mirroring doubles the length, but that appears to be an intentional convention across this toolset rather than filler.

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

Completeness3/5

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

There is no output schema, so the description carries the burden of explaining results, and 'Reports property-level identity' is only a thin hint at the response shape. For a read-only two-parameter tool this is workable but leaves an agent guessing what the comparison output contains.

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% and both parameters carry their own descriptions, including the minItems/maxItems and enum constraints, so the schema does the heavy lifting. The description restates the 2-5 range and the styles+layout default, adding no syntax or semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('compare 2-5 UI parts') and enumerates the four comparison aspects plus the default subset, so the operation is unambiguous. It does not differentiate itself from the sibling design.compare, which is the one plausible confusion an agent could have.

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 default aspects (styles + layout) imply the typical use case, but there is no explicit statement of when to pick this over design.compare or when to inspect parts with part.inspect first. Usage is inferable rather than stated.

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