ncloud-gov-mcp-server

ncloud_set_target_group_description

Idempotent

Set or update a target group's description. Specify the target group number and description text to keep infrastructure metadata clear and current.

Instructions

Set or update the description of a target group

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": {
      "targetGroupNo": "<targetGroupNo>",
      "targetGroupDescription": "<targetGroupDescription>"
    },
    "name": "ncloud_set_target_group_description"
  }
}

Input Schema

Name	Required	Description	Default
`targetGroupNo`	Yes	Target group number
`targetGroupDescription`	Yes	Target group description

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.4/5.0

Behavior2/5

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

The description adds no behavioral context beyond what annotations already provide. Annotations state idempotentHint=true and destructiveHint=false; the description merely restates the action without mentioning permissions, side effects, or idempotency implications. There is no contradiction, but no added value.

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 clear sentence: 'Set or update the description of a target group.' It is concise and free of unnecessary detail, efficiently conveying the tool's action.

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?

Given the tool's simplicity (two required string parameters), the annotation coverage, and the absence of an output schema, the description sufficiently conveys the core operation. It could mention expected outcomes or validation, but for a setter, this is adequate.

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 parameters are already documented. The description does not add any extra meaning about the parameters (e.g., format, constraints, relationship between them), leaving the baseline at 3.

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 uses a specific verb+resource combination: 'Set or update the description of a target group.' It clearly distinguishes from sibling tools that set descriptions of other resources (e.g., ncloud_set_lb_description, ncloud_set_route_table_description).

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 alternatives. It does not mention any prerequisites, exclusions, or contrast with related tools like ncloud_change_target_group_config or ncloud_get_target_group_detail.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server