Skip to main content
Glama
Sign In
Synology MCP Server

Synology MCP Server

by rafalr100
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_container_logs

Retrieve recent log lines from a Docker container to monitor its activity and diagnose issues.

Instructions

Get recent log lines for a Docker container.

Args: name: Container name (from list_containers) lines: Number of recent log lines (default 50)

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

Input Schema

NameRequiredDescriptionDefault
nameYes
linesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It describes a read operation ('Get') but does not disclose any behavioral traits beyond retrieving logs, such as rate limits, output size, or potential truncation. The default for 'lines' (50) is helpful but minimal.

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?

The description is extremely concise: two short sentences plus the Args block. Every sentence adds value with no redundant or filler text. Arguments are clearly presented in a standard format.

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?

Given the output schema exists (not shown but context indicates it does), the description does not need to explain return values. It covers the basic purpose and parameters. It could mention that logs are from stdout/stderr, but for a simple retrieval, it is sufficiently complete.

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?

The input schema has 0% coverage (no parameter descriptions), so the description adds meaning by explaining that 'name' is the container name from list_containers and 'lines' is the number of recent log lines with a default of 50. This compensates for the schema gap.

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?

The description clearly states the action 'Get recent log lines' for a specific resource 'Docker container', which is a distinct verb-resource pairing. It differentiates from siblings like 'get_container_stats' and 'list_containers' by targeting log retrieval.

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?

The description provides a usage hint by noting that the 'name' parameter comes from 'list_containers', implying a prerequisite. However, it does not explicitly state when to use this tool vs. alternatives like 'get_container_stats' or provide when-not-to-use guidelines.

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

Deploy Server

Other Tools