ncp-mcp-server

delete_server

Deletes a specific server instance by providing the server instance number. Use this to remove an NCP server instance from your infrastructure.

Instructions

서버 인스턴스를 삭제합니다

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": {
      "serverInstanceNo": "<serverInstanceNo>"
    },
    "name": "delete_server"
  }
}

Input Schema

Name	Required	Description	Default
`serverInstanceNo`	Yes	삭제할 서버 인스턴스 번호

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 5, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It merely says 'Deletes' without mentioning permanence, reversibility, prerequisites (e.g., server must be stopped), or impact on associated resources. For a destructive operation, this is a significant transparency gap.

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, short sentence that is immediately informative and not padded with unnecessary words. It is appropriately sized for the tool's simplicity and front-loads the core action.

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?

The tool has a single parameter and no output schema, but deletion is irreversible. The description lacks essential context such as whether the action is permanent, whether associated resources are affected, or any safety warnings. This makes it incomplete for a destructive operation despite its simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for the single parameter serverInstanceNo, whose description '삭제할 서버 인스턴스 번호' (Server instance number to delete) is clear. The tool description adds no extra parameter meaning, so the baseline score of 3 applies.

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?

The description '서버 인스턴스를 삭제합니다' (Deletes the server instance) clearly states a specific verb (delete) and resource (server instance), distinguishing it from siblings like stop_server, start_server, and create_server.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through the verb 'delete', but provides no explicit when-to-use vs alternatives. Given sibling tools like stop_server and start_server, there is no guidance on when deletion is appropriate versus other lifecycle operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.