ncloud-mcp-server

ncloud_update_custom_resource

Idempotent

Update an existing custom resource in Cloud Insight by specifying its ID, name, and resource data such as server IP, project, and type.

Instructions

Update a user-defined custom resource in Cloud Insight.

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": {
      "resourceId": "<resourceId>",
      "resourceName": "<resourceName>",
      "resourceData": "<resourceData>"
    },
    "name": "ncloud_update_custom_resource"
  }
}

Input Schema

Name	Required	Description
`resourceId`	Yes	Custom resource ID to update
`resourceData`	Yes	Resource data
`resourceName`	Yes	Name of the custom resource

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

B3.4/5.0

Behavior2/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, covering the safety profile. The description adds no further behavioral context, such as whether resourceData replaces the entire resource or if the resource must exist. It does not contradict annotations, but also does not enrich them.

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?

The description is a single concise sentence of eight words, front-loaded with the verb and resource, containing no redundant or extraneous information.

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 an update operation, the description lacks critical behavioral context: it does not specify whether resourceData replaces existing data, what happens if the resourceId does not exist, or what the response contains. Even with full schema coverage, the update semantics remain ambiguous, creating a significant gap for an agent.

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?

The input schema provides descriptions for all three parameters, achieving 100% coverage. The description itself adds no extra parameter semantics beyond what the schema already conveys, matching the baseline for high schema coverage.

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 uses a specific verb 'Update' and clearly identifies the resource as 'user-defined custom resource in Cloud Insight', which distinguishes it from sibling tools like create, get, list, and delete. It unambiguously states the action performed.

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 the tool is used when an existing custom resource needs modification, but it provides no explicit when-not-to-use guidance or references to alternatives. The context is clear from the tool name and sibling set, but no exclusions or additional selection criteria are given.

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

Deploy Server