Skip to main content
Glama

system_info

Detect local CPU, RAM, storage, and GPU resources to assess available hardware before running data analysis or training models.

Instructions

Detect local CPU, RAM, storage, and GPU resources.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does convey that the operation is a local (not remote/cluster) detection pass, which implies a non-destructive read, but it never states the return shape, whether a missing GPU produces an error or an empty field, or any latency/host-dependency caveat. Reasonable but thin for a zero-annotation tool.

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 front-loaded sentence with no filler, hedges, or redundant restatement of the tool name. Every word (including "local") carries information.

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?

For a zero-parameter hardware probe with no output schema, enumerating the four detected resource classes is nearly enough for an agent to decide whether to call it. The remaining gap is that the response format is unspecified and no output schema exists to fill it in.

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. Baseline of 4 applies; the description also implicitly clarifies the scope is local-only, which is the only meaningful input-like constraint.

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

Purpose5/5

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

States a specific verb ("Detect") and an enumerated resource scope (CPU, RAM, storage, GPU) in one clause. No sibling in the listed catalog (train_baseline, inspect_dataset, export_model, etc.) does hardware discovery, so the agent can distinguish it without opening any schema.

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?

There is no explicit when-to-use or when-not-to-use text and no named alternative. Usage is only implied by the resource list, but the implication is strong: this is the hardware-capability probe an agent would call before choosing a training or inference path. Adequate but with clear gaps in routing guidance.

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