Fetch recent journald log lines for a specific service unit to troubleshoot issues. Read-only action provides quick access to service logs without shell commands.
Read-only SysKnife action GetServiceLogs. fetch recent journald log lines for a service — param: unit*
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.27.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only the 'recent' qualifier and the journald source; it does not say how much log history is returned or what happens for a stopped/unknown unit.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, with the action and purpose front-loaded before the parameter note. The 'param: unit*' shorthand is terse to the point of being cryptic, but nothing is wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and an empty input schema, the description is the only source of parameter and return-shape information, and it omits unit-name format, log window/line count, and behavior on missing units. The mismatch between 'param: unit*' and the parameterless schema is left unresolved.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema declares zero parameters (additionalProperties: true), yet the description asserts a required 'unit*' argument, leaving the agent unsure whether to pass anything. It names the parameter but gives no format (bare name vs. name.service) and no indication of valid values.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: 'fetch recent journald log lines for a service', scoped to a single service. This is clearer than the name alone and hints at the difference from the broad sibling sysknife_get_journal_log, but does not explicitly contrast the two.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this versus sysknife_get_journal_log, sysknife_get_service_status, or sysknife_collect_diagnostics, and no preconditions such as journald access or elevated privileges. The only usable cue is 'for a service', which the agent must infer.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.