Skip to main content
Glama
AiJumpOps MCP Server

AiJumpOps MCP Server

by shariatissh

jms_backup

Create a full JSON snapshot backup of all JumpServer asset permission rules and user states before changes, so you can review or restore prior configurations.

Instructions

Create a full JSON snapshot backup of all JumpServer AssetPermission rules and user states before making changes.

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_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNobefore_changes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that the capture is full and covers both permission rules and user states, which is real behavioral context. It omits any statement about where the snapshot is written, whether it overwrites a prior snapshot with the same label, size/performance implications of a full capture, or what the call returns.

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?

One sentence, no filler, with the resource scope front-loaded and the usage trigger as a trailing clause. Nothing could be removed without losing information.

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?

No output schema exists, so the description should say what a caller gets back (a snapshot reference the agent could later feed to jms_revert) and how the label is used; neither is covered. It does convey the essential scope and timing, so it is minimally usable but leaves a meaningful gap for a backup/restore workflow.

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

Parameters2/5

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

Schema coverage is 0% for the single "label" parameter, and the description never mentions it, so an agent must infer from the name and the "before_changes" default that it is a snapshot identifier. The description does not say whether duplicate labels collide or how the label is consumed downstream.

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 ("Create ... backup") and a precise resource scope ("all JumpServer AssetPermission rules and user states"), plus the output format ("full JSON snapshot"). No sibling is named as a contrast, but the scope is concrete enough to distinguish it from jms_revert or jms_permission_grant by behavior alone.

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?

"before making changes" gives a clear temporal trigger that maps directly to the sibling mutation tools (grant/revoke/asset_create). It offers no explicit exclusions or named alternative for restoring state, but the when-to-use context is unmistakable.

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