Skip to main content
Glama
AiJumpOps MCP Server

AiJumpOps MCP Server

by shariatissh

jms_revert

Revert JumpServer AssetPermission rules to a backup snapshot. Preview the exact diff with confirm=false before confirming the restore.

Instructions

Revert JumpServer AssetPermission rules back to a backup snapshot. Always call with confirm=false first to preview the exact diff!

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

Input Schema

NameRequiredDescriptionDefault
fileNoBackup filename or path (empty = latest backup)
confirmNoSet to true ONLY after explicit user confirmation of the revert diff.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description has to carry behavioral disclosure. It does communicate that this is a destructive restoration and that it supports a preview mode via confirm=false, which is meaningful beyond the schema. It does not explain permissions required, what happens to rules not in the backup, or whether the revert is reversible, so gaps remain.

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?

Two sentences, front-loaded with the action and ending with the safety-critical workflow instruction. The exclamation mark is slightly informal but the content is tight and every sentence is useful.

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

Completeness3/5

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

For a destructive restore tool with no annotations and no output schema, the definition covers the preview-confirm workflow but leaves out important context: required permissions, impact on non-backup rules, and what the preview or result looks like. It is adequate but not complete for a mutation tool of this risk level.

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?

Schema coverage is 100%, so both parameters are already documented in the schema. The description reinforces the confirm workflow and the concept of a diff preview, but adds little about the file parameter's format or behavior beyond what the schema states.

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 states a specific verb (revert) plus the exact resource and scope (JumpServer AssetPermission rules to a backup snapshot). This distinguishes it from siblings like jms_backup and jms_permission_grant, which handle backup creation and permission changes rather than restoration.

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

Usage Guidelines4/5

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

It gives clear operational guidance: always call with confirm=false first to preview the diff, and the confirm parameter note says to set true only after explicit user confirmation. There is no explicit statement on when to choose this over jms_backup or permission tools, but the workflow prerequisite is strong.

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