Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Service Logs

get_service_logs

Retrieve journal logs for a specified system service or unit, filtered by time, priority, line count, or user scope to diagnose issues and inspect recent activity.

Instructions

Journal logs for one unit.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
userNo
linesNo
sinceNoe.g. '1 hour ago', 'today', '2024-06-01 12:00'
priorityNoemerg|alert|crit|err|warning|notice|info|debug

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it discloses nothing about permissions (system journals typically need elevated privileges while user journals do not), whether the call is read-only, or any limits on how much history is returned. The single sentence adds essentially no behavioral context beyond the title.

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 and front-loaded with the resource, with no wasted words. The problem is under-specification rather than verbosity, so it earns a middling score: nothing is redundant, but the single fragment carries too little.

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?

For a five-parameter tool with no annotations, the description should at minimum clarify the unit-name argument and the user/system journal distinction. Because an output schema exists, return values need not be explained, but the gaps around input meaning and privilege requirements leave the definition inadequate.

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

Parameters2/5

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

Schema coverage is only 40%, and the description does not compensate: it never says that 'name' is the unit name, what 'user' toggles, or what 'lines' and 'priority' control. Only 'since' and 'priority' carry schema descriptions, leaving the most important arguments undocumented in both places.

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 description names the resource (journal logs) and narrows scope to a single unit, which separates it from get_service_status and the general system-info siblings. However, it is a bare noun phrase with no verb and no statement of what is returned, so the purpose is only implied.

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, no mention of prerequisites, and no differentiation from siblings such as get_service_status or get_process_info. An agent must infer entirely on its own that this is the tool for inspecting what a unit has logged.

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