Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_shutdown

Shut down the UrBackup server by requiring confirm=true, enabling a controlled stop of backup services.

Instructions

Shut down the UrBackup server. confirm=true required.

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

Input Schema

NameRequiredDescriptionDefault
confirmNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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. It does disclose that a confirmation flag gates the action, which signals destructiveness, but it says nothing about what happens to in-progress backups, whether the server auto-restarts, what permissions are needed, or whether the action is reversible. For a server-wide shutdown, those omissions matter.

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?

Two short sentences, action stated first, critical constraint second. There is no filler and nothing is buried.

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?

An output schema exists, so return values need not be described. However, a destructive, unannotated, server-level operation with 0% parameter coverage warrants more than one sentence of consequence: impact on running backups, required privileges, and post-shutdown state are all missing.

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 schema itself marks no required parameters while defaulting confirm to false. The description adds real meaning by stating 'confirm=true required', telling the agent the call will not take effect without explicitly setting it — information the raw schema actively obscures.

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

Purpose4/5

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

States a specific verb and resource: 'Shut down the UrBackup server.' An agent can immediately tell this is a server-level lifecycle operation, not a backup or file operation. It does not distinguish itself from urbackup_stop_process, which is the nearest potential confusion, but the resource-level scope is clear enough without it.

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 statement of when to use this versus alternatives, no prerequisites, and no warning about conditions under which it should not be called (e.g., while backups are running). The only usage-like content is the 'confirm=true required' mechanic, which is an invocation constraint rather than selection guidance.

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