Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

calibrate

Reports simulator window, bezel, and display geometry plus button centers in screen coordinates, verifies mapped points and optional grid taps, and can save a raw screenshot.

Instructions

Report window, bezel and display geometry plus every button centre mapped to screen coordinates, and check each point is inside the window. Optionally save a raw screenshot.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calibrate"
  }
}

Input Schema

NameRequiredDescriptionDefault
gridNoGrid size per axis for verify (default: 3)
verifyNoTap a grid and report changed pixels at each point
device_idNoDevice id (defaults to active device)
save_pathNoOptional file path for a raw simulator screenshot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 burden. It does disclose a side effect (optionally writing a raw screenshot to a file path) and that it checks containment of points, which is useful. However, it omits that the verify path taps the UI (a mutating interaction) and says nothing about permissions, timing, or failure behavior, so disclosure is partial.

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?

A single dense sentence that front-loads the primary outputs (geometry and button centres) before the optional screenshot. It is efficient with no filler, though the run-on construction makes the verify/containment clause slightly harder to parse.

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 and no annotations, the description does a reasonable job of enumerating what is returned (window/bezel/display geometry, button centres, containment results). It is slightly incomplete on the side effects of the verify mode and on device selection defaults, but overall adequate for a four-parameter diagnostic tool.

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 all four parameters (grid, verify, device_id, save_path) are already documented in the schema. The description only echoes the optional screenshot behavior and adds no format or constraint detail beyond the schema, 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?

The description gives a specific verb set and resource: it reports window, bezel and display geometry, button centres in screen coordinates, and validates points inside the window, with an optional screenshot. That is far more concrete than the vague name 'calibrate'. It does not explicitly contrast itself with siblings like capture_window or get_screenshot, so it stops short of a 5.

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?

There is no statement of when to use this tool versus alternatives such as capture_window, get_screenshot or inspect_ui, and no prerequisites or exclusions. Usage is only implied by the described outputs, leaving the agent to infer the selection context.

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