Skip to main content
Glama
Systems Manager

Systems Manager

Get System Logs

sm_file_get_system_logs
Read-onlyIdempotent

Retrieves and tails system log entries, letting you specify how many lines to return for troubleshooting and monitoring host activity.

Instructions

Get system logs (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_get_system_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNoNumber of lines to tail

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description contributes nothing beyond that: it does not say which log source is read, whether tailing truncates output, or how openWorld behavior manifests. A near-zero marginal contribution over annotations earns a low score even on the relaxed bar.

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?

It is short, but the second sentence is pure filler that restates a category rather than adding information, and the lead sentence is not front-loaded with any disambiguating scope. Brevity here reflects under-specification rather than economy.

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 single-param read-only tool with full schema coverage and rich annotations, the definition is minimally sufficient to invoke correctly. However, with close siblings like query_system_logs and sm_file_tail_log_file present, the absence of any routing information leaves a real gap for correct tool selection.

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?

There is a single optional parameter with 100% schema coverage, where the schema already states default 100 and "Number of lines to tail." The description adds no meaning about behavior at boundaries (e.g., large line counts, how lines are counted). Baseline 3 is appropriate when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource ("Get system logs") is identifiable, but the second sentence, "Operations for file and log management," is a vague category label that does not distinguish this tool from siblings such as query_system_logs or sm_file_tail_log_file. The parenthetical "(sm_file_operations)" reads like an internal namespace, not a clarifying scoping statement.

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 when-to-use guidance at all, and given the presence of query_system_logs and sm_file_tail_log_file in the sibling set, the agent has no basis in the description for choosing among them. No preconditions, no exclusions, no alternatives 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