QNX Host MCP

qnx_compile_c

Compile one workspace src/name.c file for QNX x86_64 with fixed compiler arguments; it enforces a 120-second deadline and never runs the binary or accepts custom flags.

Instructions

Compile one workspace src/name.c file for QNX x86_64 with fixed compiler arguments. Never runs the resulting binary or accepts compiler flags. Deadline: 120 seconds.

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

Input Schema

Name	Required	Description	Default
`source`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A4.2/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 does well: fixed compiler arguments, no flag overrides, no post-compile execution, and a 120-second deadline. It omits what is produced or returned (object file path, diagnostics on failure) and whether prior artifacts are overwritten, which leaves meaningful gaps for a build tool.

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?

Three tight sentences with the core action, the negative constraints, and the time limit front-loaded. No filler and no 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?

For a one-parameter compile tool with no output schema and no annotations, the description covers constraints, timeout, and side-effect absence well. The main shortfall is that with no output schema it should still say what the agent receives back (artifact location or error reporting).

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 0% and the single `source` property has only a regex pattern, so the description must compensate. It clarifies that the path is workspace-relative and must be exactly one .c file under src/, which adds semantic meaning beyond the raw pattern, but it does not discuss what happens with invalid or missing files.

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 (compile), an exact resource scope (one workspace src/name.c file), and target platform (QNX x86_64) with fixed compiler arguments. This clearly separates it from siblings like qnx_image_build or qnx_toolchain_info, which operate at image or info level rather than single-file compilation.

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?

The description gives clear scoping context by ruling out flag passing and binary execution, which tells the agent this is a fixed, single-file compile step. It stops short of explicitly naming the alternative (e.g., qnx_image_build) for full builds, so the routing decision is implied rather than spelled out.

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

Deploy Server