Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

run_unit_tests

Executes Monkey C unit tests from a compiled .prg test binary in the Garmin simulator via monkeydo -t, with optional test name, device, and timeout controls.

Instructions

Run Monkey C unit tests for a compiled .prg test binary in the simulator using monkeydo -t.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prg_path": "<prg_path>"
    },
    "name": "run_unit_tests"
  }
}

Input Schema

NameRequiredDescriptionDefault
prg_pathYesPath to compiled test .prg executable
device_idNoDevice ID to execute tests on (defaults to active device)
test_nameNoOptional specific test name or suite prefix to execute
timeout_msNoMaximum execution timeout in milliseconds (default: 30000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that execution happens in the simulator using monkeydo -t, but it does not explain side effects, whether simulator state is modified, what happens on timeout, or what output the caller receives.

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?

The description is a single, front-loaded sentence with no redundant wording. Every phrase contributes to identifying the action, target, environment, and command used.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The definition is minimally adequate: it identifies the operation and environment, and the schema fully documents the four parameters. However, with no annotations and no output schema, the description should say more about execution results, state changes, or failure behavior for a tool that launches a test process.

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 the input schema already documents prg_path, device_id, test_name, and timeout_ms. The description reinforces that prg_path is a compiled test binary but adds no further meaning beyond the schema, making the baseline score appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: run Monkey C unit tests for a compiled .prg test binary in the simulator via monkeydo -t. It clearly distinguishes this from build_app, run_app, and other sibling tools because the object is explicitly a test binary and the execution mode is named.

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?

The description implies when to use the tool: when you have a compiled .prg test binary and want to execute unit tests in the simulator. It does not explicitly state when not to use it or name alternatives such as run_app, so guidance is present but incomplete.

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