Skip to main content
Glama

net_inspect_device

Collect CPU, memory, temperature, port, optical power, and latency status from one network device by device ID or IP to support health checks and troubleshooting.

Instructions

采集单台网络设备的运行状态:CPU/内存/温度/端口/光功率/时延。输入设备编号或 IP。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "device": "<device>"
    },
    "name": "net_inspect_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceYes设备编号(如 SW-CORE-01)或 IP 地址

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. The verb 采集 (collect) implies a read-only operation and the metric list discloses the scope of what is gathered, which is meaningful. However, it says nothing about authentication needs, timeout behavior for unreachable devices, rate limits, or output format.

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?

Two short sentences, front-loaded with the action and the metric scope, with zero filler. Every clause contributes 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 one-parameter read tool with full schema coverage and no output schema, the definition covers purpose and the collected metrics adequately. Minor gaps remain around failure modes and how results are returned, but nothing essential to invoking 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% for the single required parameter, and the schema already explains that 'device' accepts a device ID (e.g. SW-CORE-01) or an IP address. The description merely restates this, adding no new meaning; baseline 3 applies.

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 states a specific verb (采集/collect) and resource (single network device runtime status), then enumerates the concrete metrics returned: CPU, memory, temperature, ports, optical power, latency. This makes the tool clearly distinguishable from siblings like net_cfg_draft or net_log_analyze, though it never explicitly names or contrasts them.

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?

There is no guidance on when to use this tool versus alternatives, nor on prerequisites such as device reachability, credentials, or permissions. The only directive, '输入设备编号或 IP', is parameter formatting rather than usage guidance, leaving the agent to infer context.

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