Skip to main content
Glama

System info

system_info
Read-onlyIdempotent

Gather Windows hardware, installed developer tools, and current ZeroIDE access/permission context in one read-only call at task start, replacing several discovery commands.

Instructions

One read-only call for the context you would otherwise gather with several commands: Windows version, CPU, memory, disks, displays, user, time zone, PowerShell and installed developer tools (node, npm, python, git, dotnet, java, go, rust, docker, winget). It also says how ZeroIDE is set up for you right now: project folder, folder confinement, your access scope, which tools run freely, ask the owner first or are disabled, active temporary grants and where undo history is kept. Call it once at the start of a task.

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
noteNoShort human-readable explanation (1 line, in the user's language) of what you are about to do and why. Shown to the user on the approval card. Always provide when calling mutating tools.
agentNoShort consistent identifier or display name of this agent (e.g. 'Claude · Лендинг', 'Тесты', 'Мой агент'). Used to separate tasks and route tray messages when multiple agents work in parallel.
refreshNoProbe installed tools again instead of using the 10-minute cache.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context: a 10-minute probe cache and the fact that the result includes policy-relevant state (access scope, freely-run vs owner-approval vs disabled tools, active temporary grants, undo history location). That is meaningful behavioral disclosure beyond structured fields.

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?

Front-loaded with the core claim and the actionable instruction comes last, which is the right order. The parenthetical enumeration of developer tools is dense but functional; a few items could be trimmed without losing meaning.

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

Completeness5/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 description must carry the return-value burden, and it does so comprehensively while also covering caching and the one-shot call pattern. For a zero-required-parameter read tool, nothing an agent needs to invoke it correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters (note, agent, refresh) are already documented in the schema. The description mentions the cache behavior that motivates refresh but adds no syntax or semantics for note or agent, so the schema does the heavy lifting and this sits at the baseline.

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 and resource ('one read-only call for the context') and enumerates exactly what is returned: OS version, CPU, memory, disks, displays, user, time zone, developer tooling, plus ZeroIDE setup, access scope, tool permissions, grants and undo history. This is clearly distinguishable from siblings like run_command or read_file, which would only gather that context piecemeal.

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 trigger ('Call it once at the start of a task') and frames it as a replacement for several individual commands, which is real when-to-use guidance. It stops short of naming a sibling alternative or stating when-not to call it, so it is clear but not exhaustive.

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