ncloud-gov-mcp-server

ncloud_create_custom_resource

Create a custom resource in Cloud Insight to monitor user-defined infrastructure. Specify resource name and data including organization, project ID, server IP, and server type.

Instructions

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

Input Schema

Name	Required	Description
`resourceId`	No	Resource ID (auto-generated if omitted)
`resourceData`	Yes	Resource data
`resourceName`	Yes	Name of the custom resource
`resourceTypeId`	No	Resource type ID (default 'DEFAULT')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The description only says 'Create', implying a mutation, but does not disclose side effects, required permissions, or whether resourceId is auto-generated (though this is in the schema). The annotation destructiveHint=false adds minimal safety info, but the description itself does not enrich behavioral understanding beyond the annotation.

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?

The description is a single concise sentence with no wasted words, making it easy to scan. However, it is almost too sparse; a few more details could be included without losing 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 create tool with four parameters, a nested object, and no output schema, this description is minimal. It lacks context about Cloud Insight's custom resource model, how this tool fits with related custom resource operations, or any expectations about resource data fields. The schema covers parameter details, but the description leaves the operational context largely unexplained.

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%, so the baseline is 3. The description adds no additional parameter semantics; it doesn't explain the structure of resourceData or the relationship between resourceTypeId and resourceName. The schema itself carries the parameter documentation burden.

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?

The description clearly states the verb 'Create' and the resource 'user-defined custom resource in Cloud Insight', which differentiates it from sibling tools like list/get/update/delete. However, it doesn't clarify what a 'custom resource' is or how it relates to custom schemas, leaving some ambiguity about the exact entity being created.

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 is provided on when to use this tool versus alternatives such as ncloud_create_custom_schema or ncloud_update_custom_resource. There is no mention of prerequisites (e.g., needing an existing schema) or exclusions, so the agent lacks context for selecting this tool.

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

Deploy Server