Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

get_app_logs

Retrieve console output, System.println logs, and crash traces from a running Monkey C app and simulator, with session-file history that survives reconnects.

Instructions

Retrieve console output, System.println logs, and crash traces from the running Monkey C application and simulator. Logs are also appended to a session file, so a reconnect does not lose history.

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

NameRequiredDescriptionDefault
clearNoWhether to clear the in-memory log buffer after reading (default: false); the session file is kept
linesNoNumber of most recent log lines to retrieve (defaults to all)
since_seqNoOnly return lines newer than this sequence number (use next_seq from a previous call)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does add real behavioral value: it discloses that logs are also appended to a session file so a reconnect does not lose history, which tells the agent output is durable rather than ephemeral. It stops short of stating what happens when no app is running or whether reads block.

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 with the resource list front-loaded and the durability caveat second. No filler, no restatement of the tool name.

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 zero-required-parameter read tool with a fully documented schema and no output schema, the description supplies enough: it says what kinds of content come back and that history survives reconnects. A note on what the returned lines look like (e.g., sequence numbering implied by since_seq) would close the remaining gap.

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 three parameters (clear, lines, since_seq) are already documented in the schema, including defaults and the next_seq cross-reference. The description adds no parameter-level meaning beyond that, 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 names a specific verb ("Retrieve") and enumerates the resources returned: console output, System.println logs, and crash traces, scoped to the Monkey C app and simulator. It is clear what the tool does, though it does not distinguish itself from log-adjacent siblings like debug_status or debug_command.

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 by the phrase "from the running Monkey C application and simulator," which suggests the app must be running and that this is the diagnostic-log read path. There is no explicit when-to-use versus alternatives guidance and no stated prerequisites or failure conditions.

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