Skip to main content
Glama
Sign In
nexterm-mcp

nexterm-mcp

by X1pheR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

nexterm_create_snippet

Create a reusable Nexterm command snippet with a name, command, optional description, OS filter, and organization. Use it to save commands for repeated use across your server entries.

Instructions

Create a Nexterm command snippet. Command 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>",
      "command": "<command>"
    },
    "name": "nexterm_create_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
commandYes
os_filterNo
descriptionNo
organization_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-idempotent, open-world, non-destructive, so the safety profile is covered. The description adds one genuinely useful disclosure not in the annotations: command content is model-visible by design, which signals there is no secret/credential protection on this field. It omits organization scoping and whether the snippet is global when organization_id is null.

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, front-loaded with the action and nothing wasted. It is efficient, though the brevity is partly under-specification rather than pure concision.

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 creation tool with five undocumented parameters, no output schema, and no return-value note, the description does not supply enough for an agent to call it correctly. The visibility caveat is helpful but does not cover org scoping, os_filter semantics, or what is returned on success.

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?

Schema description coverage is 0% across five parameters, so the description must compensate and does not. It says nothing about name length limits, the command string, what os_filter values look like, or what organization_id=null means (global vs. personal), leaving every optional parameter semantically opaque.

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 ('Create a Nexterm command snippet'), which cleanly separates it from nexterm_create_script, nexterm_create_entry, and the update/delete snippet siblings. It stops short of explaining how a snippet differs from a script, which is the one ambiguity given the sibling set.

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?

No when-to-use or when-not-to-use guidance, no mention of prerequisites, and no pointer to an alternative such as nexterm_create_script or nexterm_update_snippet. The second sentence is a data-visibility note, not usage direction.

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