Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

diff_screenshot

Compare a baseline PNG against another image or the live simulator screen to get the changed percentage and bounding box of change.

Instructions

Compare a baseline PNG with another PNG or with the current simulator screen. Returns the changed percentage and the bounding box of change.

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": {
      "before_path": "<before_path>"
    },
    "name": "diff_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
thresholdNoPer-pixel channel delta that counts as changed (default: 12)
after_pathNoComparison PNG path; omit to capture the live simulator screen
before_pathYesBaseline PNG path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the return payload (changed percentage and change bounding box), which is valuable, but it is silent on side effects, permission needs, and behavior when image dimensions or formats mismatch. Adequate but far from complete for an unannotated 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?

Two tight sentences: the comparison modes first, the return values second. No filler, no repetition of the name, and everything is front-loaded.

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 usefully explains what comes back (percentage and bounding box), and the schema covers all parameters. It falls short only on error/edge-case behavior, which matters somewhat for an image comparison that can fail on size mismatch, but overall an agent has enough to invoke it correctly.

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%, so all three parameters are already documented in the input schema, including the default threshold of 12 and the omit-to-capture behavior for after_path. The description adds no syntax, format, or edge-case detail beyond what the schema provides, so the baseline of 3 applies.

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 plus resource ('Compare a baseline PNG') and clarifies the two comparison modes (second PNG vs. live simulator screen). It does not name a sibling such as get_screenshot or matrix_diff, so the agent gets no explicit disambiguation, but the operation itself is unambiguous.

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?

Usage is implied through the two modes described — pass an after_path for file-to-file comparison, or omit it to diff against the live simulator — which is a useful context signal. However, there is no statement of when this tool should be chosen over get_screenshot or matrix_diff, and no prerequisites or failure conditions are given.

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