Skip to main content
Glama
Sign In
nexterm-mcp

nexterm-mcp

by X1pheR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

nexterm_create_theme

Creates a custom Nexterm CSS theme from a name and CSS, with an optional description, to manage server appearance through Nexterm MCP.

Instructions

Create a custom Nexterm CSS theme.

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>",
      "css": "<css>"
    },
    "name": "nexterm_create_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
cssYes
nameYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already tell the agent this is a non-idempotent, non-destructive, open-world write. The description adds nothing beyond the annotations — it doesn't say what happens to existing themes, whether the created theme is activated, or what response is returned.

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 short sentence with zero waste, though its terseness is part of the under-specification problem rather than a virtue here.

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 mutation tool with three parameters at 0% schema coverage and no output schema, the description omits the parameter meanings, activation behavior, and return value. It is not complete enough to call the tool confidently.

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%, yet the description explains none of the three parameters. 'CSS theme' loosely hints that 'css' holds CSS text, but 'name' and the optional 'description' are 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 clear specific verb ('Create') and resource ('custom Nexterm CSS theme'). However, it does nothing to differentiate from sibling tools like nexterm_update_theme or nexterm_create_script, leaving the agent to infer this is the new-theme creation path.

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 guidance on when to use this versus nexterm_update_theme or nexterm_list_themes, and no mention of prerequisites such as required permissions or whether the new theme becomes active automatically.

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