Skip to main content
Glama

Get System Info

get_system_info
Read-onlyIdempotent

Reports JVM, operating-system, and hardware details so you can diagnose runtime environments and verify system configuration.

Instructions

Report JVM, operating-system and hardware information.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish a read-only, idempotent, non-destructive operation, and the description consistently adds the three categories of information reported. It does not clarify whether the data concerns the current JVM and local host, nor mention permission constraints, failure behavior, or how open-world interaction may affect the report.

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?

The single sentence is compact, grammatical, and immediately communicates the operation and its scope. No wording is redundant or distracting.

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?

For a zero-argument read-only tool, the description and annotations provide enough information to invoke it safely. Because there is no output schema, the lack of detail about returned fields or structure is a noticeable gap, and the boundaries with related environment-inspection tools remain unstated.

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 has no parameters, so there are no argument meanings or formats for the description to explain. The empty schema is sufficient for correct invocation, meeting the zero-parameter baseline.

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 clearly states the verb and information domains: reporting JVM, operating-system, and hardware information. It does not explicitly distinguish this broad system snapshot from siblings such as get_version or environment_variables.

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 implied for agents needing runtime or host environment details, and invocation is straightforward because there are no parameters. However, there is no explicit when-to-use guidance, diagnostic scenario, or direction to narrower alternatives when only version or environment-variable data is needed.

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