Skip to main content
Glama
Sign In
ncloud-gov-mcp-server

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_update_maintenance

Idempotent

Update an existing planned maintenance in Cloud Insight by changing its title, description, start/end times, or target dimensions using the maintenance ID.

Instructions

Update an existing planned maintenance schedule 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": {
      "maintenanceId": "<maintenanceId>"
    },
    "name": "ncloud_update_maintenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
descNoMaintenance description
titleNoMaintenance title
endTimeNoEnd time in Unix epoch milliseconds
startTimeNoStart time in Unix epoch milliseconds
dimensionsNoTarget dimensions
maintenanceIdYesPlanned maintenance ID to update

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/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. The description adds minimal behavioral context beyond the word 'existing', which is redundant given the required maintenanceId parameter. No mention of side effects, permissions, or return details.

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 sentence with no redundant words. It is concise and front-loaded with the core action and resource.

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 relatively simple update tool with a 100% schema coverage and non-destructive/idempotent annotations, the description is minimally sufficient. However, it does not explain the behavior of the 'dimensions' nested object, nor does it mention what the tool returns, leaving some gaps for the 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?

Schema description coverage is 100%, so all parameters are already documented with descriptions. The description does not add additional meaning to any parameter, but the schema handles the semantics adequately.

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 clearly states the verb 'Update' and the resource 'existing planned maintenance schedule', which is specific and distinguishes from sibling create/delete/list/get tools. It also adds context 'in Cloud Insight'.

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 creating, deleting, or listing maintenance schedules. The description merely states the action without mentioning alternatives or prerequisites.

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