Skip to main content
Glama
Sign In
nexterm-mcp

nexterm-mcp

by X1pheR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

nexterm_delete_integration

Destructive

Permanently removes a Nexterm integration by its ID. Use it to clean up integrations you no longer need, with deletion applying immediately.

Instructions

Permanently delete a Nexterm integration.

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": {
      "integration_id": "<integration_id>"
    },
    "name": "nexterm_delete_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
integration_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/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 'Permanently', reinforcing irreversibility, but does not describe cascade effects, permissions, or post-delete response. No contradiction.

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?

Single front-loaded sentence with no filler. The brevity contributes to gaps captured elsewhere, but structurally it is efficient and clear.

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 destructive open-world mutation, the definition states permanence but omits confirmation requirements, permission needs, and effect on linked data. With annotations covering destructive status and a simple one-parameter schema, it is minimally usable but not complete.

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?

The sole parameter integration_id has 0% schema description coverage. The description implies an integration identifier but never explains format, source, or consequences of an invalid ID, so it does not compensate for the missing schema documentation.

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?

Names a specific verb ('delete') and resource ('Nexterm integration') and adds permanence. It distinguishes from get/sync/start integration siblings, though it does not explicitly contrast named alternatives.

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?

Gives no when-to-use, prerequisites, or alternatives. An agent must infer that it is the deletion counterpart to get_integration/sync_integration, with no warning about when not to use.

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