embedded-mcp

Overview Schema Source Related Servers Discussions Admin

ssh_tail

Fetch the most recent log lines from a remote board's log file over SSH. Returns specified number of lines instantly with UTF-8 boundary protection and non-blocking operation.

Instructions

Fetch the most recent log lines from the remote log file (e.g. enor.log) via SSH ring buffer.

Instantly returns latest lines with UTF-8 boundary protection, non-blocking.

Args: board_id: The identifier of the board (e.g. 'e1_linux_host') lines: Number of recent lines to retrieve (default: 200)

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

Input Schema

Name	Required	Description	Default
`lines`	No
`board_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 9, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure; it usefully discloses that the operation is non-blocking and returns UTF-8-safe lines. However, it does not state whether an ssh_connect session is required, whether any connection state changes, or what happens on connection failure.

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 compact, front-loaded with the main purpose, and uses a clear Args block for parameters. The behavior sentence earns its place by adding non-blocking and UTF-8 boundary details without unnecessary exposition.

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?

For a simple retrieval tool this is mostly sufficient: purpose, behavior, and both parameters are covered, and an output schema exists to document return values. Still, the description omits connection prerequisites and the source/path of the log file, which matter when siblings include ssh_connect and ssh_exec.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully compensates by explaining both parameters: board_id as an identifier with an example, and lines as the count of recent lines with its default. This is additional meaning beyond the bare schema types and default.

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 uses a specific verb ('Fetch') and identifies the resource ('most recent log lines from the remote log file via SSH ring buffer'), so the agent knows exactly what the tool returns. It also contrasts implicitly with serial-focused siblings like serial_tail and with ssh_exec, which is for executing commands rather than tailing a log.

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 phrase 'via SSH ring buffer' and 'remote log file' imply this is the tool for non-blocking SSH log tailing, but it does not explicitly say when to prefer it over serial_tail or ssh_exec, nor does it mention prerequisites such as an established SSH connection.

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