Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

ncloud_create_role

Create an IAM role for Naver Cloud to hold policies, choosing Server, Account, or Service type. Use dryRun to preview the role before creating it.

Instructions

Create a new IAM role. A role is only a container for policies: creating it grants nothing until policies are attached (POST /api/v1/roles/{roleNo}/policies) and a role target is set (POST /api/v1/roles/{roleNo}/entities/account for Account roles, /entities for Server and Service roles) — those endpoints have no MCP tool yet. Use dryRun=true to preview without creating.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags as a key-value map, max 20 per resource. Example: {"env":"dev","team":"a"}
dryRunNoIf true, returns a preview without actually creating the role
descContNoDescription of the role (0-300 bytes)
roleNameYesRole name (3-100 chars: Korean/Japanese/English letters, digits, '.', '_', '-'; must start with a letter)
roleTypeYesRole type: Server (VPC server resource, no access key needed), Account (grants the main account's console/portal access to a sub account via role switching), Service (inter-service access)
isMyAccountNo⚠️ Ignored — createRole has no isMyAccount field, so this value is NOT sent. It belongs to the separate 'add Account role target' API (POST /api/v1/roles/{roleNo}/entities/account). Kept only for backward compatibility
sessionExpirationSecNoSession expiration time in seconds: 600, 1800, 3600, or 10800. REQUIRED when roleType is Account

Schema Changelog

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

  1. Changed8 schema fields changedv1.12.0
    • changedInput schema / properties / descCont / description
      Previous value: -"Description of the role"New value: +"Description of the role (0-300 bytes)"
    • changedInput schema / properties / isMyAccount / description
      Previous value: -"Whether the role applies to the current account"New value: +"⚠️ Ignored — createRole has no isMyAccount field, so this value is NOT sent. It belongs to the separate 'add Account role target' API (POST /api/v1/roles/{roleNo}/entities/account). Kept only for backward compatibility"
    • changedInput schema / properties / roleName / description
      Previous value: -"Role name (3-100 chars, letters/numbers/special chars . _ -, must start with letter)"New value: +"Role name (3-100 chars: Korean/Japanese/English letters, digits, '.', '_', '-'; must start with a letter)"
    • changedInput schema / properties / roleType / description
      Previous value: -"Role type: Server (VPC server), Account (console/portal access), Service (inter-service access)"New value: +"Role type: Server (VPC server resource, no access key needed), Account (grants the main account's console/portal access to a sub account via role switching), Service (inter-service access)"
    • changedInput schema / properties / sessionExpirationSec / description
      Previous value: -"Session expiration time in seconds (600, 1800, 3600, or 10800). Not allowed for Server type."New value: +"Session expiration time in seconds: 600, 1800, 3600, or 10800. REQUIRED when roleType is Account"
    • addedInput schema / properties / sessionExpirationSec / enum
      Added value: +[
+  600,
+  1800,
+  3600,
+  10800
+]
    • 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"
+}
    • changedInput schema / required
      Previous value: -[
-  "roleName",
-  "roleType",
-  "isMyAccount"
-]New value: +[
+  "roleName",
+  "roleType"
+]
  2. First observedv1.10.1

TDQS

A4.2/5.0
Behavior4/5

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

With only destructiveHint=false in annotations, the description carries meaningful weight: it discloses that creating a role has no immediate permission effect and that subsequent required actions are unavailable via MCP. It also documents dryRun as a preview mode, adding 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences deliver the core action, the key caveat about roles being empty containers, the unavailable follow-up endpoints, and the dryRun recommendation with no wasted words. The primary purpose is front-loaded and each sentence earns its place.

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?

The description captures the most important contextual risk (role creation grants nothing) and clearly states that policy attachment and role-target endpoints are not exposed as MCP tools, which is critical for an agent planning subsequent steps. Since there is no output schema, the omission of return-format details is acceptable. It doesn't address authorization requirements, but the parameter schema covers the remaining operational details.

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 all seven parameters, including roleType and sessionExpirationSec, are already fully documented in the schema. The description adds only a minor dryRun usage hint and does not provide significant additional parameter meaning beyond what the schema supplies. A baseline of 3 is appropriate.

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 opens with 'Create a new IAM role,' clearly identifying the verb and resource. It further distinguishes itself from sibling policy/group tools by explaining that a role is only a container that grants nothing until policies and targets are attached, making its exact scope unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description clearly conveys that this tool only creates the role shell and that the necessary follow-up steps (policy attachment and role target setting) have no MCP tool yet, so an agent won't mistakenly expect full IAM setup. It also advises using dryRun=true for a no-side-effect preview. However, it stops short of naming alternative sibling tools or explicit when-not-to-use conditions.

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