Skip to main content
Glama

Router system information

get_system_info
Read-only

Retrieve router model, firmware, uptime, CPU and memory load, plus installed KeeneticOS components to determine supported features and assess memory pressure.

Instructions

Model, firmware version, uptime, CPU and memory load, and the list of installed KeeneticOS components. Call this first when you need to know what the router supports: the component list tells you which features exist on this device. Judge memory pressure by memoryAvailableKb, not memoryFreeKb: free excludes the page cache the kernel releases on demand, so it is always low on a healthy router.

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 observedv0.0.0-dev

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so safety is covered; the description adds real interpretive value beyond them by explaining that the component list reflects device capabilities and by warning that memoryFreeKb is misleading because it excludes reclaimable page cache. It does not say how current the snapshot is (e.g., whether uptime reflects a reboot) or whether the call is expensive, which keeps it below a 5.

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?

Three sentences, front-loaded with the payload contents, followed by the usage trigger, then the memory interpretation caveat. Every sentence carries information an agent would otherwise lack; nothing is redundant.

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?

With no output schema, the description carries the burden of describing returns and does so for the main fields, including a non-obvious interpretation rule. It stops short of enumerating all fields the component list may contain or the exact shape of the response, leaving a small residual gap for a zero-argument inspection tool.

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 the baseline of 4 applies; there is no parameter semantics to add. The description's discussion of memoryAvailableKb versus memoryFreeKb concerns return values rather than inputs and does not affect this dimension.

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?

Names a specific resource and enumerates exactly what it returns: model, firmware version, uptime, CPU and memory load, and installed KeeneticOS components. This is clearly distinguishable from siblings like get_config_state or get_internet_status, which cover configuration and connectivity rather than device capability.

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 this first when you need to know what the router supports,' tied to a concrete downstream purpose (discovering which features exist). It does not name an alternative or state when not to call it, but the positive guidance is unambiguous.

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