Skip to main content
Glama

system_info

Read-onlyIdempotent

Inspect a QNX 8.0 target's release, architecture, CPU, memory, and observed SSH capabilities to verify system details for diagnosis.

Instructions

Inspect QNX 8.0 release, architecture, CPU, memory and observed SSH capabilities.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYes
statusYes
warningsNo
target_idYes
truncatedNo
observed_atYes
schema_versionNo1.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds a little nuance with 'observed SSH capabilities', hinting at active probing rather than pure static config reads, but it never explains what 'observed' means, whether the probe can fail or be slow, or whether results are cached. With rich annotations the bar is lower, so a 3 is appropriate.

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?

One front-loaded sentence with the most important scope words first and no filler. Every clause names a distinct inspection target, so nothing needs trimming.

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?

An output schema exists, so return values need not be described, and with zero parameters the input side is trivially complete. The only residual gap is the ambiguous 'observed SSH capabilities' phrasing, which an agent may not fully interpret before calling.

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 the baseline is 4. There is nothing for the description to disambiguate, and the description correctly focuses on what is inspected rather than on nonexistent inputs.

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 ('Inspect') plus the exact resource scope: QNX 8.0 release, architecture, CPU, memory, and observed SSH capabilities. This enumerated scope makes it trivially distinguishable from siblings like list_processes or read_system_log, which target different resources.

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 enumerated scope (an agent wanting host/platform facts would pick this), but there is no explicit when-to-use, when-not-to-use, or named alternative among read_system_log / list_processes / read_file. Nothing is misleading, but routing must be inferred.

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