Skip to main content
Glama

router_logs

Read-onlyIdempotent

Retrieve router system logs newest first, then filter by module, severity level, or MAC/text to diagnose DHCP, PPP, and system issues.

Instructions

System log, newest first. module: e.g. DHCPD, PPP, DHCPC, SYSTEM. contains: text or a MAC to look for. max_severity: 0 emerg, 3 err, 4 warn, 6 info, 7 debug (everything). Note: the router clears it on reboot.

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": "router_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
moduleNo
containsNo
max_severityNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so safety is covered. The description adds genuinely new behavior: results are newest-first, and the log is wiped on reboot, which tells the agent the data is ephemeral and ordering is fixed.

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?

Four short fragments, front-loaded with the resource and ordering, then parameter semantics, then the volatility caveat. It is telegraphic but every line carries information; nothing is padding.

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?

An output schema exists, so return values need no explanation. With four optional parameters, the description covers three of them plus volatility and ordering; the missing piece is what limit does and whether it caps result size.

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?

Schema description coverage is 0%, so the description must carry the parameter meaning and it largely does: module is a log facility with examples, contains is free text or a MAC, and max_severity is mapped to concrete numeric levels with 7 meaning everything. Only limit is left unexplained.

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?

"System log, newest first" states the specific resource and its ordering, which is enough for an agent to know this retrieves log entries rather than mutating anything. It does not distinguish itself from siblings such as router_status, so it stops short of a 5.

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 module and contains fields signal that this is the tool for filtered log inspection, and the reboot note hints at volatility. There is no explicit when-to-use statement, no exclusion, and no named alternative for general router state.

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