Skip to main content
Glama
Sign In
nexterm-mcp

nexterm-mcp

by X1pheR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

nexterm_create_script

Create a Nexterm script with a name and content, optionally setting a description, OS filter, or organization ID. Use it to add reusable automation scripts to a Nexterm server.

Instructions

Create a Nexterm script. Script content is model-visible by design.

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>",
      "content": "<content>"
    },
    "name": "nexterm_create_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
contentYes
os_filterNo
descriptionNo
organization_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, non-idempotent, open-world mutation, so the safety profile is covered structurally. The description adds one piece of context — that script content is 'model-visible by design' — which hints at a content-exposure consideration but is cryptic and does not say what happens on duplicate names or what permissions are needed.

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?

Two short sentences with the operation front-loaded and no wasted words. The second sentence is terse to the point of being opaque, but the overall size is appropriate.

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

Completeness2/5

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

For a five-parameter mutation tool with no output schema and zero parameter documentation, the description is far too thin — it omits return behavior, duplicate handling, os_filter format, and organization scoping. The single visibility note does not compensate for those gaps.

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?

Schema description coverage is 0% across five parameters, so the description carries the full burden and provides nothing: no explanation of 'os_filter' semantics, 'organization_id' scoping, or the distinction between 'name' and 'description'. The second sentence does not map to any parameter.

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 ('Create a Nexterm script'), which is unambiguous about the operation. It does not, however, distinguish this tool from the closely named sibling nexterm_create_snippet, so an agent must infer the difference from the schemas.

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 tool versus nexterm_create_snippet, nexterm_update_script, or nexterm_create_source, nor any mention of prerequisites such as organization membership. The agent is left to infer usage entirely from the name.

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

Deploy Server

Other Tools