Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425

ncloud_create_sub_account

Create a new IAM sub account on Naver Cloud Platform, setting access permissions, password policies, and API/console access, with a dry-run preview option.

Instructions

Create a new sub account (IAM user). Use dryRun=true to preview without creating.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memoNoDescription (0-300 bytes)
nameYesSub account username (2-30 chars)
tagsNoTags as a key-value map, max 20 per resource. Example: {"env":"dev","team":"a"}
emailNoEmail address (6-100 chars)
dryRunNoIf true, returns a preview without actually creating the sub account
loginIdYesLogin ID (3-60 chars, English letters/numbers/special chars . @ - _, must start with letter)
passwordNoLogin password (8-16 chars, required if needPasswordGenerate is false)
isMfaMandatoryNoWhether two-factor authentication is required
apiAllowSourcesNoAllowed API access sources. Only applied when useApiAllowSource is true
canConsoleAccessYesWhether to enable console access
consolePermitIpsNoAllowed console access IP ranges. Only applied when useConsolePermitIp is true
needPasswordResetYesWhether to notify password change on first login
useApiAllowSourceNoRestrict API access to specific sources. true: only apiAllowSources may call the API, false: any source
useConsolePermitIpNoRestrict console access to specific IP ranges. true: only consolePermitIps may sign in, false: any IP
canAPIGatewayAccessYesWhether to enable API Gateway access (creates access key)
needPasswordGenerateNoIf true, auto-generate password. If false, must provide password manually.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv1.12.0
    • addedInput schema / properties / apiAllowSources
      Added value: +{
      +  "description": "Allowed API access sources. Only applied when useApiAllowSource is true",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "source": {
      +        "description": "Access source value — an IP address/range for type IP, or an instance number for VPC/VPC_SERVER",
      +        "type": "string"
      +      },
      +      "type": {
      +        "description": "Access source type — IP: single IP or CIDR range, VPC: a VPC in use, VPC_SERVER: a server in a VPC",
      +        "enum": [
      +          "IP",
      +          "VPC",
      +          "VPC_SERVER"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "type",
      +      "source"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / consolePermitIps
      Added value: +{
      +  "description": "Allowed console access IP ranges. Only applied when useConsolePermitIp is true",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / tags
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "description": "Tags as a key-value map, max 20 per resource. Example: {\"env\":\"dev\",\"team\":\"a\"}",
      +  "type": "object"
      +}
    • addedInput schema / properties / useApiAllowSource
      Added value: +{
      +  "description": "Restrict API access to specific sources. true: only apiAllowSources may call the API, false: any source",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / useConsolePermitIp
      Added value: +{
      +  "description": "Restrict console access to specific IP ranges. true: only consolePermitIps may sign in, false: any IP",
      +  "type": "boolean"
      +}
  2. First observedv1.10.1

TDQS

A3.6/5.0
Behavior4/5

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

The description states that dryRun=true previews without actually creating, which directly informs the agent about a safe testing mode for an otherwise mutating operation. The annotation only says destructiveHint=false, which is mildly contradicted by the fact that creating a sub account is a significant write action, but dryRun is disclosed. It doesn't mention that canAPIGatewayAccess creates an access key, but the schema covers that partially. Overall the description adds useful behavioral context beyond the annotation.

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 sentences, concise and front-loaded with the core purpose. The dryRun hint is a useful addition without bloat. It loses one point for not adding any other high-value guidance that could fit in the same space.

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?

Given 16 parameters, nested objects (apiAllowSources), and no output schema, the description is minimal. The schema carries most of the load, and the description doesn't explain the interplay between canAPIGatewayAccess and access key creation, or the password generation flag. It's adequate but not complete for a complex creation tool.

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 all 16 parameters. The description adds no new parameter-level meaning except pointing to dryRun. Thus a baseline 3 is appropriate; it doesn't compensate with extra context because none is needed.

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 'Create a new sub account (IAM user)' uses a specific verb and resource, and clarifies the domain concept by equating sub account with IAM user. It doesn't explicitly distinguish from sibling tools like ncloud_create_sub_account_access_key, but the core action is clear.

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?

The description implies usage by saying 'Use dryRun=true to preview without creating,' which gives a testing path. However, it doesn't state when to use this vs alternatives like creating an access key or when dryRun should be used in a workflow. It provides no explicit when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sjk4425/ncloud-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server