Skip to main content
Glama

router_logs

Read-onlyIdempotent

Read and filter a TP-Link router's system log by severity, type, text, or timestamp to diagnose DHCP, WAN, and other network issues without altering the router's log settings.

Instructions

Read the router's system log (newest first when timestamps parse). Filters: level (minimum severity, e.g. WARNING), type (e.g. DHCPD, WAN), contains (text), since ('2026-11-17 08:00:00'), limit. Never changes the router's own log filter.

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
typeNo
levelNo
limitNo
sinceNo
revealNoShow secrets (passwords/keys) unmasked.
routerNoWhich router (see router_status 'routers'); default main.main
containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond them: the best-effort sort order ("newest first when timestamps parse") and the reassurance that the router's own log filter is not modified — a side effect an agent would otherwise worry about for a log tool.

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 compact paragraph, front-loaded with the verb and resource, then a tight parenthetical filter list, then the non-mutation guarantee. No filler sentences and no restating of the tool name.

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?

With seven parameters, no output schema, and 29% schema coverage, the description leaves one meaningful hole: it never says what a returned log entry looks like or how results are truncated when limit is hit. For a read-only tool this is a moderate gap rather than a blocking one, since the filter semantics are well covered.

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 coverage is only 29%, so the description must carry the load, and it does for the five undocumented filters: level is defined as minimum severity with a WARNING example, type gets DHCPD/WAN examples, since gets an explicit timestamp format, and contains and limit are characterized. The remaining two (reveal, router) are described in the schema itself, so the union is close to complete.

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 opens with a specific verb and resource ("Read the router's system log") and immediately qualifies ordering ("newest first when timestamps parse"). It does not name a sibling to distinguish itself from — router_journal, device_log, and system are all plausible neighbors — but the phrase "Never changes the router's own log filter" narrows it to a non-mutating read.

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?

It enumerates the filter dimensions, which implies when to reach for it, and it points at router_status 'routers' for the router parameter. However, it never says when to prefer router_journal or device_log, nor does it state any exclusion (e.g., that this is not for configuration history). Usage is inferable but not explicit.

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