mcp-1panel-plus

Overview Schema Source Related Servers Discussions Admin

Get Bounded Docker Container Logs

get_container_logs

Read-only

Fetch recent, bounded, ANSI-stripped Docker container logs from a selected 1Panel node with inline secret redaction for troubleshooting.

Instructions

Fetch recent tail logs from a Docker container on the selected node (bounded to at most 500 lines / 64 KiB, ANSI-stripped, with inline secret redaction).

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

Input Schema

Name	Required	Description	Default
`tail`	No	Maximum number of tail lines to fetch (1-500, default 100).
`since`	No	Optional log window filter (e.g. "1h", "24h", or "").
`nodeId`	No	Target node ID: "local" for the Main Node, or a numeric string ID (e.g. "3") from list_nodes.	local
`container`	Yes	Exact container name on the selected node.
`timestamp`	No	Include Docker log timestamps.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The description adds useful behavioral context beyond annotations: it specifies that logs are bounded to at most 500 lines / 64 KiB, ANSI-stripped, and have inline secret redaction. These are important traits for an agent to know when interpreting output. However, it doesn't mention error behavior or performance characteristics, leaving some gaps.

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 a single, well-structured sentence with zero waste. It front-loads the core action and immediately follows with important constraints and processing details. Every segment earns its place.

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 tool's relative simplicity, full schema description coverage, and the presence of read-only annotations, the description is nearly complete. It covers bounds and redaction but does not mention potential failure modes (e.g., container not found) or return format details, though the latter is less critical without an output schema.

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 description coverage is 100%, so the schema already fully documents all five parameters including defaults and constraints. The description does not add any syntax or format details beyond what the schema provides, so the baseline score of 3 is appropriate.

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 states a specific verb ('Fetch') and resource ('recent tail logs from a Docker container on the selected node'), making the tool's function immediately clear. It doesn't explicitly distinguish itself from sibling tools like list_containers or get_child_node_upgrade_logs, but the resource and action are distinct enough for an agent to identify the operation.

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 implied by the phrase 'Fetch recent tail logs' and the scoping to 'a Docker container on the selected node', but there is no explicit when-to-use guidance versus alternatives such as get_child_node_upgrade_logs or operate_container. No exclusions or prerequisites are mentioned.

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