Skip to main content
Glama
Sign In
nexterm-mcp

nexterm-mcp

by X1pheR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

nexterm_delete_theme

Destructive

Permanently remove a custom Nexterm theme by theme ID, enabling cleanup of obsolete or unwanted themes.

Instructions

Permanently delete a custom Nexterm 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": {
      "theme_id": "<theme_id>"
    },
    "name": "nexterm_delete_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
theme_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds one useful behavioral fact not in the annotations: only *custom* themes can be deleted (built-ins presumably cannot). It does not say what happens to a theme that is currently active or how the call fails for a non-existent id.

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

Conciseness5/5

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

A single front-loaded sentence with zero filler; the critical word "Permanently" appears before the resource name.

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 one-parameter destructive tool with annotations carrying the safety hints and no output schema, the definition is minimally sufficient. It still leaves out error/precondition behavior (active theme, missing id) and how the id is sourced, which an agent invoking a permanent delete would want.

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% and the single parameter theme_id has no descriptive text in the schema. The description never mentions the id or how to obtain it, so it does not compensate for the coverage gap; the implied link to "custom" themes is only indirect.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Permanently delete a custom Nexterm theme"), and the qualifier "custom" scopes it in a way an agent can distinguish from sibling deletes like nexterm_delete_source or nexterm_delete_tag. No other theme-deletion tool exists in the sibling list, so ambiguity is minimal.

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 versus nexterm_update_theme, nexterm_set_active_theme, or leaving the theme alone. It also doesn't state a precondition such as whether the theme must be inactive or whether the caller should look up the id via nexterm_list_themes first.

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