Garmin Connect IQ Simulator MCP Server

Overview Schema Source Related Servers Discussions Admin

get_app_logs

Retrieve console output, System.println logs, and crash traces from a running Monkey C app and simulator to debug issues.

Instructions

Retrieve console output, System.println logs, and crash traces from the running Monkey C application and simulator.

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

Input Schema

Name	Required	Description	Default
`clear`	No	Whether to clear the log buffer after reading (default: false)
`lines`	No	Number of most recent log lines to retrieve (defaults to all)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries full behavioral burden. 'Retrieve' implies a read, and the mention of a 'running' app hints at a launch prerequisite, but nothing discloses that the optional clear flag mutates/discards the buffer, whether polling is rate-limited, or whether reading is side-effect free.

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?

A single front-loaded sentence that states the action and the three data categories without filler. Nothing redundant or trailing.

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?

For a two-optional-parameter read tool with no output schema and no annotations, the description covers the source and content of the data adequately. Minor gaps remain around return ordering/format and the destructive effect of clear, but nothing critical to invoking it correctly is missing.

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 both the 'clear' buffer flag and the 'lines' limit/defaults are already fully documented in structured data. The description adds no distinguishing parameter detail (such as ordering or what 'all' means in practice), so the baseline 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?

Names a specific verb ('Retrieve') and enumerates the exact resources returned: console output, System.println logs, and crash traces. The scope (running Monkey C application and simulator) makes it obviously distinct from siblings like get_screenshot or simulator_status, though it never explicitly contrasts itself with an alternative tool.

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 only implied: an agent infers this is the tool for debugging output from a running app. There is no explicit statement of when to reach for it versus inspecting UI state or checking simulator_status, and no prerequisites such as 'the app must already be launched' are stated.

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