Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

matrix_diff

Compare baseline PNGs in a directory against matching current PNGs to report changed percentage and bounding boxes for visual regression checks.

Instructions

Compare every baseline PNG in a directory with the matching current PNG and report changed percentage and bounds.

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": {
      "baseline_dir": "<baseline_dir>"
    },
    "name": "matrix_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
thresholdNoPer-pixel channel delta (default: 12)
output_dirNoDirectory containing current PNGs (default: sibling 'current')
baseline_dirYesDirectory containing baseline PNGs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool compares PNGs and reports changed percentage and bounds, but does not explain side effects, error handling for missing current PNGs, output persistence, matching rules, or whether it writes diff artifacts. This is a meaningful gap for a file-processing comparison tool.

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?

The description is a single front-loaded sentence with no redundant wording. It states the core operation and reported outputs efficiently.

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

Completeness2/5

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

Given the absence of annotations and an output schema, the description should be more complete. It names two reported metrics but does not describe the return format, what happens when a matching current PNG is missing, or whether any files are written, leaving important context for correct invocation unclear.

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%, with all three parameters documented in the schema including defaults for threshold and output_dir. The description does not add meaning beyond the schema, such as how threshold affects matching or how output_dir is used in practice, so the baseline of 3 is appropriate.

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?

The description uses a specific verb and resource: compare every baseline PNG in a directory with the matching current PNG and report changed percentage and bounds. It is clear what the tool does, but it does not explicitly distinguish this batch-directory comparison from the sibling diff_screenshot tool.

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?

The description implies a batch use case by saying 'every baseline PNG in a directory,' but gives no explicit guidance on when to use this instead of diff_screenshot or other alternatives. There are no stated exclusions, prerequisites, or conditions for selecting this tool.

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