Skip to main content
Glama
Sign In
nexterm-mcp

nexterm-mcp

by X1pheR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

nexterm_delete_organization

Destructive

Permanently deletes a Nexterm organization using its required organization_id. Use it to remove obsolete or unwanted organizations from the Nexterm server.

Instructions

Permanently delete a Nexterm organization.

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": {
      "organization_id": "<organization_id>"
    },
    "name": "nexterm_delete_organization"
  }
}

Input Schema

NameRequiredDescriptionDefault
organization_idYes

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 destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is carried structurally; the description usefully reinforces irreversibility with 'Permanently'. It does not disclose what cascades (members, entries, sessions) or what permissions are required.

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?

One front-loaded sentence with zero padding. Brevity is appropriate, though it borders on under-specification rather than true conciseness.

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 destructive, non-idempotent, open-world deletion with no output schema, the description omits side effects, required permissions, and any recovery path. An agent has enough to call it but not enough to call it safely.

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% for the single required organization_id parameter, and the description never mentions it or how to obtain a valid id. With one documented-by-type-only parameter, the description should have compensated and does not.

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 ('Permanently delete a Nexterm organization'), which distinguishes it from the other delete_* siblings that target sources, entries, folders, tags and scripts. Clear, though it does no explicit sibling naming.

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 alternatives such as nexterm_list_organizations or nexterm_get_organization, and no preconditions or confirmation advice before an irreversible operation. The only usage signal is the word 'Permanently'.

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