Skip to main content
Glama
synology-mcp
by r03eRt

NAS logs (Log Center)

get_system_logs
Read-only

Retrieve and filter Synology NAS logs from Log Center—system or connection events—by level, keyword, and date to troubleshoot sign-ins, services, and disk issues; newest entries first.

Instructions

Entries from the NAS's own logs (Log Center): 'system' (services, certificates, disks, updates…) or 'connection' (sign-ins, failed logins, by user and IP). Filter by level, text and dates. Newest first. Needs a DSM administrator account.

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_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date, ISO; a bare date includes the whole day
fromNoStart date, ISO (e.g. 2026-11-01)
typeNoWhich log (default system)
levelNoOnly this level
limitNoMax entries (default 50)
offsetNo
keywordNoText to look for in the message

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds genuinely new behavioral context: results are newest-first, and a DSM administrator account is required (an auth prerequisite the annotations do not convey). It says nothing about volume limits or pagination behavior, which would matter for a 7-param log query.

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 compact sentences: scope and default first, then filtering axes and ordering, then the auth prerequisite. Every clause carries information and nothing is padded.

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 read-only filtered-list tool with no output schema, the description covers scope, filters, ordering and auth. It does not sketch what an entry looks like or how limit/offset interact across pages, which is the main remaining gap.

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 coverage is 86%, so the baseline is 3 and the schema already documents most parameters including the enum values. The description does add real meaning for `type` by explaining what each log class contains, and confirms the filtering axes (level, text, dates), but leaves `offset`/paging behavior undiscussed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource ("the NAS's own logs (Log Center)") and enumerates its two scopes with parenthetical content examples, so an agent can tell this apart from notification- or file-oriented siblings without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The two log types are described concretely ('system' = services/certificates/disks/updates, 'connection' = sign-ins/failed logins by user and IP), which tells the agent which one to pick, and the admin-account prerequisite is stated. No explicit exclusion or named alternative (e.g. get_notifications for alerts) is given, so it stops short of full routing guidance.

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