Skip to main content
Glama
sandbanks

Agentic_SSH

tail_container_logs

Retrieve the tail end of logs from a Docker container on one or multiple remote hosts concurrently, with options for line count and timestamps.

Instructions

Fetch the last N lines of logs from a remote Docker container on a single host ('host') or multiple hosts concurrently ('hosts'). If using 'hosts', returns a JSON map mapping hostnames to their success status and container log output. Prefer 'hosts' to query container logs across multiple machines simultaneously.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoThe target hostname or IP address
hostsNoA list of hostname targets to query concurrently
linesNoNumber of lines to read from the end (default: 100)
containerYesThe Docker container name or ID
timestampsNoIf true, includes timestamps in output (default: false)
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses return format for 'hosts' (JSON map) but not for single host. Does not mention error handling, default host behavior, or permissions. Adequate but not thorough.

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 succinct sentences, front-loaded with main action. No wasted words.

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?

Missing detail on behavior when neither host nor hosts specified (both optional in schema). No output schema, so return format for single host is unclear. Adequate for a simple read tool but has gaps.

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 parameters are already documented. Description adds minimal extra meaning (e.g., JSON map for hosts) but is largely redundant. Baseline 3 is appropriate.

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 (fetch logs) and resource (remote Docker container), distinguishing between single and multiple hosts. It differentiates from sibling 'tail_log' which is for file logs.

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?

Provides clear context when to use 'hosts' vs 'host', preferring 'hosts' for multiple machines. Lacks explicit when-not-to-use or alternative tools, but context is sufficient given sibling names.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandbanks/agentic_ssh'

If you have feedback or need assistance with the MCP directory API, please join our Discord server