Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

place_window

Move or clamp the simulator window within the nearest monitor work area. Call without coordinates to rescue a window that is mostly off-screen.

Instructions

Move or clamp the simulator window inside the nearest monitor work area. With no coordinates it only rescues a window that is mostly off-screen.

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": "place_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
widthNo
heightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the clamping semantics and the restricted no-argument behavior, but omits whether a call is a no-op when the window is already on-screen, whether it requires a running simulator/session, and what it returns.

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 sentences, front-loaded with the core action and followed by the important edge-case behavior. No filler, no redundancy.

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?

For a four-parameter tool with no annotations and no output schema, the definition leaves half the parameters undefined and says nothing about preconditions or results. It explains the headline behavior well but is not complete enough to call the tool confidently with coordinates.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters. The description only implies that x/y are optional 'coordinates'; width and height are never mentioned, nor are units, coordinate origin, or whether width/height resize the window rather than reposition it.

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 pair ('move or clamp') on a specific resource ('the simulator window'), and adds the target frame of reference ('nearest monitor work area'). An agent can distinguish this from siblings like capture_window or list_windows without opening the schema, though it does not explicitly name a contrasting sibling.

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?

It gives a concrete conditional for the zero-argument case: with no coordinates it only rescues a window that is mostly off-screen. That tells the agent when the no-arg invocation is appropriate, but there is no guidance on when to supply coordinates versus use another window-management sibling.

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