Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

system_info

Read-only

Retrieve OS, uptime, CPU cores, load average, memory, and swap usage from a remote Linux server to assess health and capacity.

Instructions

Get OS, uptime, CPU cores, load average, memory and swap usage for a server.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "server": "<server>"
    },
    "name": "system_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

The readOnlyHint and destructiveHint annotations already establish the safety profile, so the description's main added value is disclosing which metrics come back. It says nothing about whether the target server must be connected, whether the call is cheap or slow, or how failures surface. That is thin but not misleading for a read-only probe.

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 sentence, front-loaded with the verb and a compact enumeration of returned fields. Nothing is padded and nothing needs reordering.

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

Completeness3/5

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

There is no output schema, so the metric list is useful, but the definition never explains the sole required parameter or the connection prerequisite. For a one-parameter read-only tool that is adequate rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required 'server' parameter, so the description carries the full burden and does not meet it. It never says what form 'server' takes (hostname, IP, ID from list_servers) or that it identifies the target host. The only clue is the phrase 'for a server'.

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 opens with a specific verb, 'Get', and enumerates the exact resources returned: OS, uptime, CPU cores, load average, memory and swap. That set of metrics distinguishes it from siblings like disk_usage or process_list, 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 Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for host-level health/resource questions. There is no statement of when to prefer it over disk_usage or process_list, and no prerequisite such as needing an active session via connect_server/start_session.

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