Skip to main content
Glama
Sign In
keenetic

keenetic

by Kykyryky23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Системная информация

get_system_info

Retrieve Keenetic router system status, including uptime, CPU load, and memory usage, to diagnose device health and performance.

Instructions

Аптайм, загрузка, память и т.п.

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.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the behavioral burden. It implies a read-only retrieval of telemetry by naming informational fields, but it does not explicitly disclose that no side effects occur, nor does it describe output format, rate limits, or authentication requirements.

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?

The description is a single concise sentence that places the key examples up front. The phrase 'и т.п.' is somewhat low-information, but overall there is no unnecessary repetition or verbose phrasing.

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-parameter informational tool, the description is minimally sufficient: an agent can infer that calling it yields system-level telemetry. Still, because there is no output schema and the description relies on vague examples, the exact contents and structure of the returned system info remain incomplete.

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 accepts zero parameters and schema description coverage is 100%, so there is no parameter ambiguity to explain. The baseline of 4 applies because no parameter details are needed.

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 names the resource as system information and gives concrete content examples: uptime, load, memory. However, it lacks an explicit verb and the trailing 'etc.' leaves the exact scope vague, and it doesn't distinguish this from nearby get-like siblings such as get_version or get_wan_status.

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?

No guidance is given about when to use this tool versus alternatives like get_version or get_wan_status. The description only enumerates information categories and provides no exclusions, prerequisites, or decision heuristics.

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

Deploy Server

Other Tools