qnx-mcp

Overview Schema Source Related Servers Discussions Admin

Start a QNX target

target_start

Idempotent

Boots an existing QNX target without rebuilding and waits for root SSH to answer with the pinned host key. If it is already running, only waits for SSH.

Instructions

Boot an existing target (no rebuild) and wait until root SSH answers with the target's pinned host key. Idempotent: if it is already running it only waits for SSH.

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": {
      "name": "<name>"
    },
    "name": "target_start"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Target name such as 'tb' (lowercase letters, digits, '-', '_'); must be inside the server allowlist
`boot_timeout_s`	No	Seconds to wait for SSH

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Goes beyond the annotations by disclosing that SSH readiness is verified against the target's pinned host key and that the call blocks until then, plus a concrete idempotency behavior ('only waits for SSH'). It does not say what happens on timeout expiry or whether a failed boot leaves partial state, which would be the remaining behavioral gap.

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 action and its completion condition front-loaded, followed by the idempotency note. No filler or repetition of schema content.

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 an output schema present, return values need no explanation, and the description covers the key non-schema facts: no rebuild, SSH host-key verification, and idempotent behavior. Timeout failure semantics are the one omission that would matter to an agent.

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 both parameters are already documented with descriptions, defaults, and bounds. The description only indirectly contextualizes boot_timeout_s by framing the tool as waiting on SSH; it adds no format or naming detail beyond the schema.

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?

States a specific verb and resource ('Boot an existing target') plus the completion condition ('wait until root SSH answers'). The parenthetical 'no rebuild' explicitly separates it from build/deploy_and_run, and 'existing target' separates it from target_create.

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?

Implies the correct usage context: the target must already exist (created via target_create) and the boot is not a rebuild (rules out build/deploy_and_run). It also explains that calling it on a running target is safe, removing the need to check target_status first. It stops short of naming target_status/target_create as explicit alternatives.

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