nexterm-mcp

Overview Schema Source Related Servers Discussions Admin

nexterm_create_entry

Creates a Nexterm server entry from typed connection fields, letting you register SSH, RDP, VNC, or other endpoints with name, IP, port, protocol, and optional folder/identity settings.

Instructions

Create a Nexterm server entry using typed connection fields.

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": {
      "name": "<name>",
      "ip": "<ip>"
    },
    "name": "nexterm_create_entry"
  }
}

Input Schema

Name	Required	Default
`ip`	Yes
`icon`	No
`name`	Yes
`port`	No
`vmid`	No
`protocol`	No	ssh
`renderer`	No
`folder_id`	No
`node_name`	No
`mac_address`	No
`identity_ids`	No
`rdp_security`	No
`jump_host_ids`	No
`keyboard_layout`	No
`organization_id`	No
`monitoring_enabled`	No
`wake_on_lan_enabled`	No
`wol_broadcast_address`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 29, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations already indicate this is a non-read-only, non-idempotent, open-world creation operation. The description adds almost no behavioral context beyond that, such as what happens on duplicate name/IP, required permissions, validation behavior, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no wasted wording. However, it is too terse for a tool with 18 parameters and complex connection semantics, so conciseness comes at the cost of useful detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 18-parameter creation tool with no output schema and no schema field descriptions, the description is far too sparse. It omits required-field guidance, protocol-specific behavior, identity/folder organization fields, and expected return or failure behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 18 parameters and 0% description coverage, so the description must compensate by explaining parameter meaning. It only says "typed connection fields" and does not clarify required fields like name and ip or protocol-specific options like rdp_security and jump_host_ids.

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 states a clear verb and resource: "Create a Nexterm server entry." It distinguishes the tool from sibling operations such as create_folder or create_tag, but the phrase "typed connection fields" is vague and does not further clarify scope.

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 guidance on when to use this rather than nexterm_update_entry, nexterm_duplicate_entry, or nexterm_import_ssh_config. The description implies creation but gives no prerequisites, exclusions, or alternative-selection criteria.

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

Deploy Server