Skip to main content
Glama
Sign In
QNX Host MCP

QNX Host MCP

by martinPisacreta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

qnx_toolchain_info

Reads the configured QNX compiler version and available targets using fixed commands to verify toolchain setup without installing or activating the SDP.

Instructions

Read QNX compiler version and available targets using fixed commands. Does not install or activate the SDP. Deadline: 30 seconds.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full load. It discloses that the operation is read-only, that commands are fixed, that nothing is installed or activated, and that there is a 30-second deadline, which is solid. However, it says nothing about failure behavior or error reporting, and those gaps matter for an environment-probing 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 short sentences, with the read action first, scope exclusions next, and the deadline last. Every sentence carries information and there is no filler.

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 parameterless read tool, the description covers what is returned (compiler version and available targets) and the timeout. It lacks detail on output format, but the tool's simplicity limits the cost of that gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has zero parameters, which sets a baseline of 4. The phrase 'fixed commands' reinforces that the tool takes no input, so no further parameter explanation is needed.

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?

The description gives a specific verb and resource: read QNX compiler version and available targets. It also distinguishes itself from siblings implicitly by stating it does not install or activate the SDP, but it does not name the compile or image tools it complements.

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?

It tells the agent what this tool does not do and fixes a 30-second deadline, which is useful context. But it never states when to call it, such as before qnx_compile_c or when a target or version is unknown, so usage is only implied.

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

Deploy Server

Other Tools