Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_create_custom_schema

Create a user-defined Cloud Insight schema for custom metrics by defining fields, data types, and exactly one identifying dimension under a Custom/ product name.

Instructions

Create a user-defined custom schema in Cloud Insight for custom metrics. prodName must start with "Custom/" (e.g. "Custom/MyProduct"); include exactly one dimension with idDimension=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsYesSchema field definitions (FieldDto[])
prodNameYesSchema (product) name, must start with "Custom/" (e.g. "Custom/MyProduct")
useCustomResourceNoWhether to use custom resource (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changedv2.0.1
    • changedInput schema / properties / fields / description
      Previous value: -"Schema field definitions"New value: +"Schema field definitions (FieldDto[])"
    • addedInput schema / properties / fields / items / properties / aggregations
      Added value: +{
+  "additionalProperties": {
+    "items": {
+      "enum": [
+        "COUNT",
+        "SUM",
+        "MAX",
+        "MIN",
+        "AVG"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "description": "Metric fields only: aggregation functions per interval, e.g. {\"Min1\": [\"AVG\"], \"Min5\": [\"AVG\",\"MAX\"]}",
+  "propertyNames": {
+    "enum": [
+      "Min1",
+      "Min5",
+      "Min30",
+      "Hour2",
+      "Day1"
+    ]
+  },
+  "type": "object"
+}
    • addedInput schema / properties / fields / items / properties / counter
      Added value: +{
+  "description": "Counter metric (default false)",
+  "type": "boolean"
+}
    • addedInput schema / properties / fields / items / properties / dataType
      Added value: +{
+  "description": "Data type (dimension fields must be STRING)",
+  "enum": [
+    "STRING",
+    "INTEGER",
+    "LONG",
+    "FLOAT"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / fields / items / properties / desc
      Added value: +{
+  "description": "Field description",
+  "type": "string"
+}
    • changedInput schema / properties / fields / items / properties / dimension / description
      Previous value: -"Whether this field is a dimension"New value: +"true if this field is a dimension (default false)"
    • removedInput schema / properties / fields / items / properties / fieldName
      Removed value: -{
-  "description": "Field name",
-  "type": "string"
-}
    • removedInput schema / properties / fields / items / properties / fieldType
      Removed value: -{
-  "description": "Field data type",
-  "enum": [
-    "STRING",
-    "INTEGER",
-    "LONG",
-    "FLOAT"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / fields / items / properties / idDimension
      Added value: +{
+  "description": "Dimension used to identify resources in event rules (exactly one dimension must be the idDimension)",
+  "type": "boolean"
+}
    • addedInput schema / properties / fields / items / properties / metric
      Added value: +{
+  "description": "true if this field is a metric (default false)",
+  "type": "boolean"
+}
    • addedInput schema / properties / fields / items / properties / metricType
      Added value: +{
+  "description": "Metric type",
+  "enum": [
+    "BASIC",
+    "EXTENDED",
+    "CUSTOM"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / fields / items / properties / name
      Added value: +{
+  "description": "Field name",
+  "type": "string"
+}
    • changedInput schema / properties / fields / items / required
      Previous value: -[
-  "fieldName",
-  "fieldType"
-]New value: +[
+  "name",
+  "dataType"
+]
    • addedInput schema / properties / fields / minItems
      Added value: +1
    • changedInput schema / properties / prodName / description
      Previous value: -"Product name(s) for the custom schema"New value: +"Schema (product) name, must start with \"Custom/\" (e.g. \"Custom/MyProduct\")"
    • removedInput schema / properties / prodName / items
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / prodName / pattern
      Added value: +"^Custom\\/"
    • changedInput schema / properties / prodName / type
      Previous value: -"array"New value: +"string"
  2. First observedv1.10.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations provide only destructiveHint=false, so the description carries most of the behavioral burden. It usefully states the naming constraint and the exactly-one-idDimension rule, which shape a valid payload, but it says nothing about whether creation conflicts with an existing schema, whether it is idempotent, or what happens on validation failure.

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?

Two tight sentences with the purpose front-loaded and constraints following; nothing is wasted. It slightly over-compresses by packing two hard requirements into one line, but it remains readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create tool with no output schema and thin annotations, the description covers the name pattern and the structural dimension rule, which are the main pitfalls. It is complete enough to invoke correctly, with only edge-case behavior (conflicts, error handling) left unspecified.

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 schema already documents prodName's ^Custom\/ pattern and the idDimension "exactly one" rule. The description restates both rather than adding new syntax or format detail, so baseline 3 applies.

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?

States a specific verb+resource ("Create a user-defined custom schema") and scopes it to Cloud Insight custom metrics, so the agent knows exactly what the tool produces. It does not, however, distinguish itself from nearby siblings such as ncloud_get_product_schema, ncloud_update_product_schema, or ncloud_delete_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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the mention of "custom metrics" hints at the custom-monitoring scenario, but there is no explicit when-to-use, no prerequisites, and no routing to or away from the sibling schema tools. An agent could infer context but must guess the boundaries.

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