Skip to main content
Glama
nucleusv

Linux MCP daemon

by nucleusv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

system/os-release

Read-onlyIdempotent

Retrieve Linux distribution and kernel version from /etc/os-release and uname; read-only output helps identify the running OS for diagnostics or automation.

Instructions

Returns the Linux distribution and kernel version: the contents of /etc/os-release plus the uname line (system, host name, release, version, machine). Read-only. In a containerized daemon /etc/os-release is the container image's, not the host's. Text has an OS Release Info: block with the raw file and a Kernel Info: line; output_format: json (also yaml/table/wide) returns an object with os_release (the raw file text, not parsed into fields) and kernel (the uname line). For CPU details use cpu/list, for kernel parameters kernel/system-control.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
output_formatNoUse json for structured output (yaml, table and wide return the same JSON); default is text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.1
    • changedInput schema / properties / output_format / description
      Previous value: -"Desired output format (e.g. json, yaml, table, wide). Defaults to text"New value: +"Use json for structured output (yaml, table and wide return the same JSON); default is text"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent behavior, and the description adds genuinely material context beyond them: the containerization caveat that /etc/os-release reflects the image rather than the host. It also discloses the resulting output shape (OS Release Info block, Kernel Info line, JSON object keys), which the annotations cannot convey.

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?

Dense but front-loaded: purpose first, then container caveat, then output format, then sibling routing. Every sentence carries information, though the middle output-format sentence is heavy and could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by describing return content in both text and JSON modes, notes the container caveat, and points to the right siblings for adjacent data. An agent has everything needed to call it and interpret the result.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining the accepted values' behavior and what the json object actually contains (os_release raw text, kernel line). That is useful interpretation the schema does not supply.

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 and resource ('Returns the Linux distribution and kernel version') and enumerates exactly what the data comprises (/etc/os-release contents plus the uname line). It also differentiates itself from siblings by routing CPU and kernel-parameter questions elsewhere.

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?

Explicitly names alternatives with the condition that selects them ('For CPU details use cpu/list, for kernel parameters kernel/system-control'), which gives clear routing. It stops just short of a full when/when-not statement for the tool itself, so 4 rather than 5.

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