Skip to main content
Glama
io.github.crunchtools/systemd

io.github.crunchtools/systemd

by crunchtools

Hostinfo Tool

hostinfo_tool
Read-only

Retrieve the host's hostname, kernel version, and operating system details to identify and verify the system environment.

Instructions

Get host identity info: hostname, kernel, OS.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, and an output schema covers the return shape, so the description carries little burden. The 'host identity' framing adds a small amount of scope context, but nothing about locality, caching, or freshness is disclosed — acceptable but thin given what structured fields already cover.

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?

A single clause-length sentence with the verb and the three key fields front-loaded. No filler, nothing redundant.

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?

With zero parameters, readOnlyHint covering safety, and an output schema covering return values, the description is nearly sufficient. The only missing piece is routing guidance against system_status_tool, which is a minor gap for a trivial no-arg read.

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 nothing for the description to disambiguate and the baseline of 4 applies. The listed fields do not map to any input and add no confusion.

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 states a specific verb ('Get') and resource ('host identity info') and enumerates the returned facts: hostname, kernel, OS. It is clear what the tool does, but it does not distinguish itself from the closest sibling, system_status_tool, which plausibly returns overlapping system information.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Nothing says when to reach for this versus system_status_tool or any other sibling, and no prerequisites or exclusions are stated. The usage is only implied by the resource name.

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