mcp-ssh

Overview Schema Source Related Servers Discussions Admin

analyze_log_errors

Scan a remote log file for error patterns and get a concise summary of warnings, exceptions, and critical issues with counts and examples.

Instructions

Analyze a log file for error patterns and summarize findings.

Searches for ERROR, WARN, CRITICAL, Exception, and similar keywords.

Args: path: Absolute path to the log file. host_name: Named host from SSH_HOSTS config; uses default host if omitted.

Returns: Error/warning summary with counts and recent examples.

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

Input Schema

Name	Required	Description	Default
`path`	Yes
`host_name`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.5Aug 7, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It notes the tool searches for specific keywords and returns a summary with counts and examples, and mentions default host behavior. However, it does not disclose prerequisites such as needing an active SSH connection or failure modes for missing files.

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 well-structured with a one-sentence summary followed by concise Args and Returns sections. Every sentence serves a purpose, and it avoids redundant detail.

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?

The tool is moderately complex (remote file analysis, 2 parameters), and the description, combined with the output schema, covers the essential invocation details. It lacks explicit usage guidance, but the purpose is clear enough for an agent to select and call the tool correctly.

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 thoroughly explains both parameters: 'path' is an absolute path to the log file, and 'host_name' is a named host from SSH_HOSTS config with a default if omitted. This adds clear meaning beyond the schema.

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 a specific verb and resource: 'Analyze a log file for error patterns and summarize findings.' It lists search keywords (ERROR, WARN, CRITICAL, Exception) which defines the scope and distinguishes it from sibling tools like grep_file or tail_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 description implies the tool is for log error analysis and summarization, but it gives no explicit when-to-use vs alternatives. Sibling tools like tail_log and grep_file are not mentioned, and there are no exclusions or alternative recommendations.

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