Skip to main content
Glama
Sign In
QNX Host MCP

QNX Host MCP

by martinPisacreta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

qnx_image_ip

Reads the address reported for an owned QNX image via a fixed command; requires verified ownership and configuration and does not connect to the address.

Instructions

Read the address reported for an owned image using a fixed command. Requires verified image ownership and configuration; does not connect to the address. Deadline: 20 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_image_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavior: a fixed command, a verified-ownership/configuration prerequisite, no connection to the address (implying a side-effect-free read), and a 20-second deadline. It omits what happens on failure or when ownership is unverified, so the disclosure is solid but not exhaustive.

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, front-loaded with the purpose before the preconditions and the 20-second deadline. No sentence is padding; even the 'does not connect' clause removes a real ambiguity.

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 zero-parameter read tool with no output schema, the definition covers purpose, preconditions, behavioral boundary, and timing. The main gap is that it never states the form of the returned address or how failures surface, which the absent output schema would otherwise have handled.

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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies the target image is identified by prior ownership state rather than by an argument.

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 the address reported for an owned image'. An agent can tell this apart from qnx_image_start/stop/build without opening the schema. It stops short of naming the sibling tools or restating the exact scope of 'owned image' in the toolchain, so it is clear but not maximally distinguishing.

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?

Usage is implied by the precondition 'Requires verified image ownership and configuration', which tells the agent when the tool is applicable. The clause 'does not connect to the address' usefully rules out one misreading (this is not a connectivity probe), but no explicit alternatives are named for the opposite case, leaving the agent to infer that qnx_image_start or other tools handle connection.

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