Skip to main content
Glama
AiJumpOps MCP Server

AiJumpOps MCP Server

by shariatissh

jms_check_access

Check whether a JumpServer user can access a specific asset and reveal the permission rules, accounts, and actions that apply.

Instructions

Check whether a specific JumpServer User currently has access to a specific Asset, and show which permission rules, accounts (e.g. root, ubuntu), and actions apply.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user": "<user>",
      "asset": "<asset>"
    },
    "name": "jms_check_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesUsername, display name, email, or ID
assetYesAsset name, IP address, or ID

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?

No annotations are supplied, so the description carries the full burden. It usefully discloses what the response covers (applicable permission rules, accounts like root/ubuntu, actions), but says nothing about whether group or node-inherited permissions are resolved, whether this is a live evaluation or cached, or what happens when the user or asset is unknown.

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?

A single well-formed sentence with the action and scope front-loaded and zero redundant wording. 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?

With two simple parameters and no output schema, the description does sketch the returned content, which helps. However, it omits resolution semantics (group/node inheritance) and failure behavior, which matter for an access-evaluation tool an agent may rely on for authorization decisions.

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%, and the schema already explains that 'user' accepts username, display name, email, or ID and 'asset' accepts name, IP, or ID. The description only restates that these are 'specific' entities, adding no new meaning beyond the schema, so the baseline of 3 applies.

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 a specific verb and resource — checking whether a given JumpServer User has access to a given Asset — plus the evaluated scope (permission rules, accounts, actions). It is clearly distinguishable from broad listing tools like jms_permissions_list, but it never explicitly contrasts itself with any sibling, so it lands at 4 rather than 5.

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?

Usage is only implied: the word 'Check' plus the user+asset scope suggests pre-grant verification or troubleshooting scenarios, but there is no explicit when-to-use, no exclusions, and no pointer to alternatives such as jms_permissions_list for a global view.

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