Skip to main content
Glama

sysinfo

Read-only

Retrieve OS, CPU, memory, free disk, GPU, and PATH developer tool versions to diagnose system capabilities and environment.

Instructions

OS, CPU, memory, free disk, GPU, dev tool versions on PATH.

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

Input Schema

NameRequiredDescriptionDefault
gpuNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

C2.4/5.0
Behavior2/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, so the description's added value should be the traits annotations cannot express — but it says nothing about latency (PATH scanning and GPU probing can be slow), whether the gpu flag changes behavior, or what form the report takes. 'On PATH' is the only hint of behavioral substance.

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

Conciseness3/5

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

It is a single, front-loaded phrase with no padding, but it is telegraphic rather than structured prose, so the compactness costs clarity instead of earning it.

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

Completeness2/5

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

With no output schema, no parameter documentation, and no annotations beyond readOnlyHint, the description carries the burden of explaining the return shape and the gpu flag, and it does neither. For a multi-source diagnostics tool this is too thin to let an agent call it confidently.

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?

The single boolean parameter 'gpu' has 0% schema description coverage, and the description lists GPU as one of the always-reported items, implying it is included unconditionally. It therefore adds no clarity about what toggling gpu actually does and arguably muddies it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the resources reported (OS, CPU, memory, free disk, GPU, dev tool versions on PATH), which gives a concrete picture of the output, but it is a noun fragment with no verb and no statement that this is a read-only system-information report. It also overlaps with the sibling disk_usage on 'free disk' without saying how they differ.

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?

There is no when-to-use guidance, no mention of when to prefer disk_usage or env_compare instead, and no note about prerequisites or cost. The agent must infer the tool's role purely from the field list.

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