Skip to main content
Glama
AiJumpOps MCP Server

AiJumpOps MCP Server

by shariatissh

jms_permissions_list

List JumpServer AssetPermission rules and filter by user, asset, or search query to review who can access what.

Instructions

List JumpServer AssetPermission (authorization) rules, optionally filtered by user, asset, or search query.

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

Input Schema

NameRequiredDescriptionDefault
userNoFilter permissions for a specific user
assetNoFilter permissions for a specific asset
limitNo
searchNo

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; the verb "List" implies a read-only, non-destructive operation, which is useful. However, it does not disclose pagination behavior, what the default limit of 200 means, or whether results are truncated, leaving meaningful behavioral gaps.

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 front-loaded sentence with zero filler; the resource is named first and the optional filters follow immediately.

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 simple read-only list tool with no output schema, the definition covers purpose and filters adequately. It falls short on the undocumented limit/pagination parameter and on any hint about result shape, which an agent would need to page correctly.

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 50%: user and asset are documented in the schema, and the description reinforces that these act as filters. The search parameter is named but given no format semantics, and the limit parameter is undocumented in both schema and description.

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 and resource: "List JumpServer AssetPermission (authorization) rules," and clarifies what AssetPermission means. It is clearly distinguishable from grant/revoke siblings by the "List" verb, though it never explicitly names those alternatives.

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 phrase "optionally filtered by user, asset, or search query" implies when the tool is useful, but there is no explicit when-to-use/when-not guidance or routing to jms_permission_grant / jms_permission_revoke / jms_check_access for related tasks.

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