TrueNAS MCP

System Info

system_info

Retrieves TrueNAS system information—version, hostname, uptime, CPU, and memory—for monitoring, inventory, and troubleshooting.

Instructions

Get TrueNAS system information (version, hostname, uptime, CPU, memory).

Returns: JSON string with system.info fields.

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

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It implicitly identifies a read-only snapshot query and the 'Returns: JSON string' line confirms no mutation or side effects, but it says nothing about permissions/auth needs, cost, or freshness of the data. For a trivial no-arg read, this is adequate but thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the purpose and followed by the return shape; nothing extraneous. The 'Returns' line is mild duplication given an output schema exists, which keeps it short of a 5.

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 no-argument read tool with a documented output schema, the description covers everything needed to select and invoke it. Only auth/permission expectations are unaddressed, a minor gap given the simplicity.

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. The description correctly requires no argument explanation and instead spends its words on the returned payload.

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 (Get TrueNAS system information) and enumerates the exact fields returned (version, hostname, uptime, CPU, memory), so an agent knows precisely what it gets. It does not explicitly distinguish itself from siblings, but none of the list_* tools overlap with system-level info.

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?

The name and description together make the use case obvious (read system-wide status), but there is no explicit when-to-use guidance, no mention of alternatives such as truenas_call for other system endpoints, and no stated prerequisites. Usage is implied rather than specified.

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