Skip to main content
Glama
Connect IQ MCP

Connect IQ MCP

by idoo

Session logs

sim_logs
Read-onlyIdempotent

Retrieve Garmin simulator state and incremental monkeydo session log lines after a cursor, with exit and crash flags; fetch parsed CIQ_LOG.YML crash entries when needed.

Instructions

Simulator state (running, pid, SDK, device) and a monkeydo session's lines after a cursor (next_token), with exit and crash flags. Default: newest session. crash:true returns the newest parsed CIQ_LOG.YML entries.

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

Input Schema

NameRequiredDescriptionDefault
afterNocursor: return lines after this (next_token of the previous call)
crashNoreturn the newest parsed CIQ_LOG.YML entries (error, details, app, file:line stack) instead of session lines
limitNomax lines, default 500; with crash: newest entries, default 3
session_idNodefault: newest session

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context: cursor-based pagination via next_token, defaulting to the newest session, and default limits of 500 lines (3 crash entries). It does not explain whether paging is exhaustive or what happens when a session is still running.

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?

Two dense sentences with no filler, and the primary capability is front-loaded before the crash-mode variant. The parenthetical style is compressed but readable; nothing extraneous is present.

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 carries the burden of describing returns, and it does so reasonably: state fields, session lines with exit and crash flags, and crash entries with error, details, app and file:line stack. Only minor gaps remain, such as behavior on a live or terminated session.

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 every parameter is already documented in the input schema, including defaults and the crash redirect. The description largely restates that same information (next_token cursor, newest-session default, crash mode) without adding format or edge-case meaning, 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 specific resources and outputs: simulator state fields (running, pid, SDK, device), a monkeydo session's lines after a cursor, and exit/crash flags. It is clearly a read/inspection tool distinct from action siblings like sim_run and sim_stop, though it never states that contrast explicitly.

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?

Provides mode-selection guidance ('Default: newest session', 'crash:true returns the newest parsed CIQ_LOG.YML entries instead of session lines') and the cursor pattern for continued reads. It does not say when to prefer this over sibling inspectors such as sdk_info or sdk_device_get, so usage is implied rather than explicit.

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