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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_update_product_schema

Idempotent

Update a custom schema in Cloud Insight by providing product name, product key, and revised field definitions. Modify field names, types, and dimensions to align with your monitoring data.

Instructions

Update a user-defined custom schema 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": {
      "prodName": "<prodName>",
      "cw_key": "<cw_key>",
      "fields": "<fields>"
    },
    "name": "ncloud_update_product_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
cw_keyYesProduct key (cw_key) of the schema to update
fieldsYesUpdated schema field definitions
prodNameYesProduct name of the schema to update

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/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 minimal context by specifying 'user-defined custom schema' and 'Cloud Insight,' but does not disclose whether the update replaces the entire schema definition, merges with existing fields, or has any side effects. With annotations present, the bar is lower, but the description still lacks behavioral nuance beyond what annotations provide.

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, front-loaded sentence with no redundant words. It directly communicates the purpose without extraneous content.

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?

With complete schema documentation and annotations present, the description is adequate for a simple update tool. However, it does not clarify whether the 'fields' parameter represents a full replacement of the schema's field definitions or a partial update, which is a meaningful gap. No output schema exists, but that is consistent with many update operations.

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 full descriptions for all three parameters (prodName, cw_key, fields) including nested field objects, achieving 100% schema coverage. The description itself adds no additional parameter information, 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 clearly states the verb "Update" and the resource "user-defined custom schema in Cloud Insight," which precisely identifies the tool's action and scope. It distinguishes itself from related tools like ncloud_create_custom_schema, ncloud_delete_product_schema, and ncloud_get_product_schema.

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?

The description provides no guidance on when to use this tool versus alternatives such as creating, deleting, or getting a schema. It does not mention any prerequisites, exclusions, or conditions under which updating is appropriate.

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