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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_change_fabric_cluster_description

Idempotent

Change a fabric cluster's description to clarify its purpose in your infrastructure. Set the cluster number and new description, or omit the description to clear it.

Instructions

Change a fabric cluster's description

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": {
      "fabricClusterNo": "<fabricClusterNo>"
    },
    "name": "ncloud_change_fabric_cluster_description"
  }
}

Input Schema

NameRequiredDescriptionDefault
fabricClusterNoYesFabric cluster number to update
fabricClusterDescriptionNoNew description for the fabric cluster (up to 1000 bytes; omit to clear)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior2/5

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

The description simply says 'Change a fabric cluster's description' and adds no behavioral context beyond what the annotations (idempotentHint, destructiveHint) already indicate. It does not mention the optional clear behavior or byte limit, though these are present in the schema.

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 extraneous words, making it highly concise and appropriately sized for the tool's simplicity.

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?

The description is minimal but sufficient for a simple mutation tool given the rich schema and annotations. It could mention that the description is optional and clearing, but that is already in the schema. Overall, it is adequate but lacks contextual depth.

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%, with fabricClusterNo and fabricClusterDescription already described. The description adds no additional parameter semantics, 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?

The description clearly states the action (change) and resource (fabric cluster's description), distinguishing it from sibling tools like ncloud_change_fabric_cluster_name. However, it adds little beyond the tool name itself and lacks explicit scope or alternative references.

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 ncloud_change_fabric_cluster_name for name updates. It does not mention any prerequisites, exclusions, or context for when this tool 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