Skip to main content
Glama

net_log_analyze

Analyzes device logs to detect link disconnections, optical degradation, communication timeouts, weak passwords, and physical-layer packet errors, then provides remediation suggestions.

Instructions

分析一段设备日志,按规则识别断链、光衰、通讯超时、弱口令、物理层错包等问题并给出处理建议。

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": {
      "log": "<log>"
    },
    "name": "net_log_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
logYes日志原文(多行)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 disclose the analysis is rule-based and that output includes actionable handling suggestions, which implies a read-only analytical operation. However, it omits whether the log is stored or transmitted, size/length limits, and whether findings come back with severity or confidence, so significant behavioral gaps remain.

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 that states the action, the resource, the detection scope, and the deliverable with no filler. The enumeration of fault types earns its space because it defines the tool's coverage boundary.

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 single-parameter analyzer with no output schema, the description should say more about the shape of the result (structured findings list, severity, suggested actions) and about input limits. It conveys the intent adequately but leaves the agent guessing at output structure and constraints.

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?

Only one parameter exists and schema coverage is 100%, so the schema already documents 'log' as multi-line raw log text. The description adds no format, encoding, or size guidance beyond that, so the 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 names a specific verb+resource ('分析一段设备日志') and enumerates the exact fault classes it detects (断链、光衰、通讯超时、弱口令、物理层错包) plus the deliverable (处理建议). It is clearly distinguishable from siblings like net_ticket_create or net_cfg_draft, though it doesn't explicitly contrast itself with net_inspect_device.

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?

Usage is only implied: the agent can infer it should call this when it has raw device log text that needs fault triage. There is no statement of when NOT to use it, no mention of alternatives (e.g. net_inspect_device for live device state), and no prerequisites or log-size/format constraints.

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