Skip to main content
Glama
Systems Manager

Systems Manager

Tail Log File

sm_file_tail_log_file
Read-onlyIdempotent

Reads the last lines of a specified log file to inspect recent entries for troubleshooting and monitoring.

Instructions

Tail log file (sm_file_operations). Operations for file and log management

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sm_file_tail_log_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNoNumber of lines to tail
filepathNoPath to file

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say what is returned, what happens with a large file, or what occurs when filepath is left null — which is a real behavioral question given the nullable default.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the text is short, but roughly half of it is namespace filler ("sm_file_operations", "Operations for file and log management") that earns no place. Brevity here reflects under-specification rather than disciplined editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters and no output schema, the description should still resolve the ambiguous nullable filepath default and hint at result shape. It does neither, leaving an agent to guess what a null path tails and what the response contains.

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%, with both "lines" and "filepath" documented in the schema, so the baseline is 3. The description contributes no additional meaning, and notably does not explain the semantic of the nullable filepath default (tail which file?) that the schema leaves open.

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?

"Tail log file" gives a specific verb and resource that an agent can act on immediately. It does not differentiate from near siblings such as sm_file_get_system_logs or sm_file_grep_files, and the trailing "(sm_file_operations) / Operations for file and log management" is namespace boilerplate rather than scope information.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to tail versus when to grep, search, or fetch system logs, even though several sibling tools operate on the same files. No prerequisites, no exclusions, no alternatives are named.

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