Skip to main content
Glama
AiJumpOps MCP Server

AiJumpOps MCP Server

by shariatissh

jms_nodes_list

Lists JumpServer asset tree nodes and asset counts so you can browse directories such as /Default/Production and /Default/Staging, with optional search.

Instructions

List JumpServer asset tree nodes (e.g. /Default/Production, /Default/Staging) and asset counts.

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

Input Schema

NameRequiredDescriptionDefault
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that the result pairs nodes with asset counts, which is genuinely useful, but says nothing about read-only safety, permissions, pagination, truncation of large trees, or behavior of the search parameter.

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 efficient sentence with the core resource front-loaded and illustrative examples appended. Nothing is wasted, though the parenthetical examples could be trimmed if routing guidance were added instead.

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 one-parameter read tool with no annotations and no output schema, the description is minimally adequate: it identifies the resource and the shape of what comes back. It falls short on the search parameter's meaning and on how this differs from the other list tools in the family.

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?

The single 'search' parameter has 0% schema description coverage, and the description never explains what it matches (node name, full path, partial substring) or whether it filters or prunes the tree. With one undocumented parameter, the description fails to compensate for the schema gap.

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 gives a specific verb and resource ('List JumpServer asset tree nodes') and clarifies the output includes asset counts, with concrete path examples (/Default/Production). It implicitly distinguishes tree nodes from flat asset listings but never names the sibling jms_assets_list, so the boundary is left to inference.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus jms_assets_list or jms_asset_inspect, and no stated prerequisites or exclusions. The path examples hint at a tree-browsing use case but do not constitute routing guidance.

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