QNX Host MCP

qnx_operation_cancel

Request cancellation of a QNX compile operation by operation ID; acceptance does not confirm process termination, so poll operation status for the final state.

Instructions

Request cancellation of an operation created by this server. Acceptance does not confirm process termination; poll operation status for the final state.

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

Input Schema

Name	Required	Description	Default
`operationId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A4/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 behavioral burden, and it discloses the single most important non-obvious trait: acceptance is asynchronous and does not confirm process termination. It does not cover idempotency, behavior on unknown or already-completed operation IDs, or error semantics, so it is strong but not complete.

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, front-loaded with the action and immediately followed by the caveat an agent most needs. No filler, nothing repeated from structured fields.

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 one-parameter, non-destructive-intent tool with no output schema and no annotations, the description covers purpose and post-call workflow adequately. It leaves out error/edge-case behavior (unknown or already-finished operation ID), which is the main 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 0% on the single parameter, so the description must compensate; it only implies that operationId refers to an operation created by this server. It adds no format, provenance, or lookup guidance (the 32-hex pattern exists only in the schema as a regex, unexplained).

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?

States a specific verb and resource ("Request cancellation of an operation") and scopes it to operations "created by this server," which tells an agent this is not a general-purpose cancel. It also implicitly routes to the sibling qnx_operation_status for final state, though it never names the sibling explicitly or contrasts itself with the other qnx_* tools.

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?

Gives clear context for use: cancel an operation previously created by this server, then poll status for the final result. It does not state prerequisites (e.g., required permissions) or when-not-to-use (e.g., operations already terminal), so it stops short of full when/when-not guidance.

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

Deploy Server