Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_create_maintenance

Schedule planned maintenance windows in Cloud Insight by specifying title, start/end times, and target resources.

Instructions

Create a new planned maintenance schedule in Cloud Insight.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descNoMaintenance description
titleYesMaintenance title
endTimeYesEnd time in Unix epoch milliseconds
startTimeYesStart time in Unix epoch milliseconds
dimensionsYesTarget resources keyed by cw_key: {"<cw_key>": [{"instanceNo": "1111", "type": "svr"}]} (PMCreateUpdateDto)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.1
    • addedInput schema / properties / dimensions / additionalProperties / items
      Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedInput schema / properties / dimensions / additionalProperties / type
      Added value: +"array"
    • changedInput schema / properties / dimensions / description
      Previous value: -"Target dimensions (resource identifiers)"New value: +"Target resources keyed by cw_key: {\"<cw_key>\": [{\"instanceNo\": \"1111\", \"type\": \"svr\"}]} (PMCreateUpdateDto)"
  2. First observedv1.10.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations only supply destructiveHint=false, so the description carries nearly the full behavioral burden. It says nothing about what creating a maintenance schedule actually does (e.g., whether it suppresses alerts during the window), required permissions, or whether the schedule takes effect immediately. For a mutation tool with nested target-resource mappings, this is a significant disclosure gap.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, but is so terse that conciseness shades into under-specification for a 5-parameter mutation tool.

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?

Given a create operation with nested target mappings, minimal annotations, and no output schema, the description should explain the effect of a maintenance window and its interaction with monitoring/alerting. Instead it repeats only the tool name's implication, leaving an agent without enough context to call it confidently.

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%, including the complex nested 'dimensions' structure with a cw_key/instanceNo/type example, so the baseline is 3 by rule. The description adds no meaning beyond the schema (e.g., what cw_key refers to or valid 'type' values).

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?

Specific verb+resource: 'Create a new planned maintenance schedule in Cloud Insight.' An agent can distinguish it from siblings like ncloud_update_maintenance, ncloud_delete_maintenance, and ncloud_get_maintenance_detail. It stops short of explicitly naming those alternatives, but the CRUD role is unambiguous.

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 when-to-use guidance, no prerequisites, no mention of when a maintenance schedule is appropriate versus alternatives. The agent gets no routing help among the create/update/delete/list maintenance siblings.

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