Skip to main content
Glama
AiJumpOps MCP Server

AiJumpOps MCP Server

by shariatissh

jms_sessions_active

List active live SSH/RDP terminal sessions on JumpServer, then terminate a selected session after an explicit confirmation preview.

Instructions

List currently active live SSH/RDP terminal sessions on JumpServer, or terminate a live session (with confirm=true after preview).

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

Input Schema

NameRequiredDescriptionDefault
userNoFilter by username
assetNoFilter by asset
confirmNoSet to true ONLY after the user explicitly confirms terminating the session.
terminate_session_idNoOptional session UUID to kill/terminate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose a safety gate (confirm=true only after user confirmation) on a destructive action, which is genuinely useful. However, it omits what terminating does to the connected user, whether it is reversible, and what privilege level is required, so coverage of the mutation's consequences is incomplete.

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?

A single front-loaded sentence covering both operating modes with no filler. The trailing parenthetical 'after preview' is slightly confusing because no preview mechanism is described, which costs it the top mark.

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 four-parameter, dual-mode tool with no output schema and no annotations, the description covers the read mode and the destructive mode adequately but leaves gaps: the undefined 'preview' step, the lack of any note on required permissions, and no hint at what a session listing contains. Enough to call it, not enough to call it confidently.

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 description coverage is 100%, so all four parameters are already documented in the schema, establishing a baseline of 3. The description only restates the confirm/terminate pairing that the schema already states and adds no format, matching, or mutual-exclusivity rules (e.g. whether terminate_session_id overrides user/asset filters).

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?

The description names both a specific verb+resource (list active live SSH/RDP terminal sessions on JumpServer) and the second mode (terminate a live session), so an agent knows exactly what the tool touches. It does not explicitly differentiate itself from any sibling, but the closest siblings (assets, users, permissions, audit) are clearly unrelated domains.

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

Usage Guidelines3/5

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

It implies a two-step flow for termination via '(with confirm=true after preview)', which is real usage guidance, but the 'preview' step is never defined and no parameter or mode performs it. There is no guidance on when to use the user/asset filters versus fetching everything, and no statement of who may terminate sessions.

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