Skip to main content
Glama
Sign In
homebutler

homebutler

by Higangssh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

system_status

Read-only

Read CPU, memory, disk usage, and uptime for a machine, locally or over SSH by server name. Refuses inside containers instead of reporting the container as the host.

Instructions

Get system status including CPU, memory, disk usage, and uptime, for the machine this binary runs on. Inside a container it refuses rather than describe the container as the host; name a server to read a machine over SSH

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverNoRemote server name from config (optional, runs locally if omitted; inside a container a local call is refused, because a container cannot see the machine it is on)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.8.0
    • changedInput schema / properties / server / description
      Previous value: -"Remote server name from config (optional, runs locally if omitted)"New value: +"Remote server name from config (optional, runs locally if omitted; inside a container a local call is refused, because a container cannot see the machine it is on)"
  2. First observedv0.10.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds real context on top: the container refusal semantics (it won't misreport a container as the host) and that remote reads go over SSH. It does not describe output shape, pagination, or any SSH auth/config failure behavior, which are minor gaps for a read-only tool.

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 dense sentences with the scope statement front-loaded and no filler. It loses a point because the container-refusal clause is stated twice in effect (once in the description, once in the schema's param text) and the semicolon construction is slightly convoluted.

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 one optional parameter, no output schema, and read-only annotations, the description covers what is needed: what is measured, where it reads from, and the local-versus-remote switch. Only SSH prerequisites and the response format are left implicit, which is acceptable for a simple read tool.

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% and the single 'server' param is already well documented, so the baseline is 3. The description nevertheless adds transport meaning beyond the schema by stating the value is read over SSH, which the schema does not mention.

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 system status') and enumerates the returned metrics (CPU, memory, disk usage, uptime), plus the crucial scope limit 'for the machine this binary runs on'. It is clearly distinguishable from container-scoped siblings like docker_stats, though no sibling is named explicitly.

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?

Gives an explicit selection rule: omit 'server' to run locally, name a server to read a machine over SSH, and a when-not case (local calls inside a container are refused). It stops short of pointing at any alternative sibling tool for container or hypervisor metrics.

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