arcane-cli-mcp

arcane_playbook

Read-only

Lists and returns safe, step-by-step workflows for Arcane homelab tasks such as updates, triage, vulnerability review, cleanup, GitOps sync, health checks, and repo deployment.

Instructions

Safe step-by-step workflows for this Arcane homelab. Call it BEFORE starting any of these tasks: checking or applying image/container updates, project triage (broken or unhealthy stacks), vulnerability review, disk cleanup or pruning, GitOps syncs, a read-only health check, or deploying a GitHub repo as a project. With no name it lists the playbooks and when to use each; with a name it returns the full playbook to follow. They encode the confirmation rules (one change at a time, stop on needs_confirmation).

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": "arcane_playbook"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely new behavioral context by stating the playbooks encode confirmation rules — one change at a time, stop on needs_confirmation. It stops short of describing output shape, but an output schema exists to cover that.

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

Conciseness4/5

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

Front-loaded with the imperative 'call it BEFORE', then the trigger list, then the two-mode semantics. The task enumeration is long but each item is a distinct, actionable trigger; wording is otherwise tight.

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?

For a single-optional-param, read-only lookup tool with an output schema, the description supplies everything needed: triggering conditions, mode semantics, and the confirmation discipline the returned playbooks impose.

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

Parameters4/5

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

Schema coverage is 0% and the single optional `name` param has no schema description, so the description must carry it — and it does, explaining both the null/list behavior and the named/full-playbook behavior, which also implies how to discover valid names. Minor gap: no guidance on name format or matching.

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?

States a specific resource (step-by-step playbooks for this homelab) and precisely distinguishes its two modes: no `name` lists the playbooks, a `name` returns the full playbook. The enumerated task coverage makes it clearly separable from reference-style siblings like arcane_docs or arcane_cli_help.

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 'Call it BEFORE starting any of these tasks' and enumerates the triggering situations (updates, triage, vulnerability review, cleanup, GitOps sync, health check, repo deploy). An agent knows exactly when to reach for this tool rather than acting directly.

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

Deploy Server