Skip to main content
Glama
AiJumpOps MCP Server

AiJumpOps MCP Server

by shariatissh

jms_audit_logs

Query JumpServer security audit logs to review executed shell commands, login events, terminal sessions, or admin changes by user, asset, date range, and search text.

Instructions

Query JumpServer security audit logs: executed shell commands ('commands'), user login events ('logins'), historical terminal sessions ('sessions'), or admin changes ('operations').

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

Input Schema

NameRequiredDescriptionDefault
daysNoLookback window in days (default: 7)
userNoFilter by username
assetNoFilter by asset name
limitNo
searchNoSearch text (e.g. 'rm -rf', 'sudo', IP)
log_typeNocommands

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/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 behavioral burden, and it discloses little beyond scope: it never says the operation is read-only, what permissions are required to read audit logs, whether results are paginated or capped, or how large a lookback is expensive. The category labels are the only behavioral signal, which is thin for an audit-log tool with no structured hints.

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 front-loaded sentence with the resource named first and the option mapping in parentheses; there is no filler, hedging, or repetition. Every clause carries information an agent needs to pick a log_type.

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?

With 6 optional parameters, no output schema, and no annotations, the description should do more than name the data categories — it omits return shape, result ordering, and how the limit interacts with the days window. It is adequate to make a first call but leaves meaningful gaps for a tool with this much surface area.

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 67%, so the schema documents most parameters, and the description adds real value by glossing what each of the four enum values actually returns — the schema lists the enum without per-value meaning. It says nothing about days, user, asset, search, or limit semantics, but those are largely self-documenting in the schema, so baseline 3 is fair.

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 ('Query') and resource ('JumpServer security audit logs'), then enumerates the four log categories with their literal log_type values, so an agent knows exactly what data domain this covers. It does not distinguish itself from the sibling jms_security_audit, which sounds like it overlaps, leaving ambiguity at the boundary.

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?

The enumeration of the four log types implicitly guides selection via log_type ('commands' for shell history, 'logins' for auth events, etc.), which is useful implied usage guidance. However, there is no explicit statement of when to prefer this over jms_security_audit or jms_sessions_active, and no prerequisites or exclusions are given.

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