Skip to main content
Glama
lacs-project

sysknife

by lacs-project
OverviewSchemaRelated ServersScoreDiscussions
Rust
Local

sysknife_plan

Convert natural-language Linux administration requests into typed, risk-rated steps with transaction IDs. Get a clear plan to review and approve in a terminal before any action runs.

Instructions

Plan a Linux system administration intent. Returns typed steps with risk levels, resolved commands, and daemon transaction IDs. IMPORTANT: Present the plan, then STOP. The user must run sysknife approve <transaction-id> in a real terminal for each accepted step. Do not execute from chat approval alone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intentYesNatural-language intent, e.g. "show disk usage" or "add vim to my system".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stepsYesOrdered list of steps to execute.
intentYesThe original natural-language intent.
summaryYesOne-line summary of the plan.
explanationYesLonger explanation of why this plan was chosen.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv0.1.5
    • addedOutput schema / $defs / PlanStepOutput / properties / current_state
      Added value: +{
+  "default": null,
+  "description": "Relevant system state as the daemon found it, before the change."
+}
    • addedOutput schema / $defs / PlanStepOutput / properties / expected_side_effects
      Added value: +{
+  "default": [],
+  "description": "Side effects the daemon expects beyond the change itself.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / $defs / PlanStepOutput / properties / proposed_change
      Added value: +{
+  "default": null,
+  "description": "What the daemon will change, as it resolved it — not as the planner\ndescribed it. This is the substance of what the operator approves."
+}
    • addedOutput schema / $defs / PlanStepOutput / properties / reboot_required
      Added value: +{
+  "default": false,
+  "description": "Whether applying this step requires a reboot to take effect.",
+  "type": "boolean"
+}
    • addedOutput schema / $defs / PlanStepOutput / properties / rollback_available
      Added value: +{
+  "default": false,
+  "description": "Whether this step can be rolled back automatically if it fails.",
+  "type": "boolean"
+}
  2. Addedv0.1.2

TDQS

A4.5/5.0
Behavior4/5

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

Description reveals the output structure (typed steps, risk levels, commands, transaction IDs) and the critical workflow constraint (stop and wait for real terminal approval). No annotations are provided, so the description carries the full burden; it does not contradict any.

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?

Three concise sentences: the first describes purpose and output, the next two provide essential usage instructions. No redundant information, well front-loaded.

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

Completeness5/5

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

Given the output schema exists, the description appropriately summarizes return types. The usage workflow is fully explained, and the single parameter is well-covered. No gaps.

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?

The single parameter 'intent' has a complete description in the schema (100% coverage). The tool description does not add additional meaning beyond that, so baseline 3 is appropriate.

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 it plans a Linux system administration intent and returns structured steps with risk levels, commands, and transaction IDs. It distinguishes from sibling tools like sysknife_execute and sysknife_audit_verify by focusing on the planning phase.

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

Usage Guidelines5/5

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

Explicitly instructs the agent to present the plan, then STOP, and requires the user to run 'sysknife approve' in a terminal. It also warns not to execute from chat approval alone, providing clear usage boundaries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lacs-project/sysknife'

If you have feedback or need assistance with the MCP directory API, please join our Discord server