Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425

ncloud_sens_send_alimtalk

Send KakaoTalk AlimTalk notifications via SENS, ensuring template compliance, with optional SMS failover and dry-run preview. Supports scheduling and batch delivery to up to 100 recipients.

Instructions

Send Alim Talk (KakaoTalk notification) messages through SENS (POST /alimtalk/v2/services/{serviceId}/messages → 202). Every field must match the approved template (content, buttons, item list). Optional SMS failover per message. Use dryRun=true to preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNoIf true, returns the request preview without sending
messagesYesRecipients (1-100)
serviceIdNoALIMTALK service ID in NRN form (e.g. ncp:kkobizmsg:kr:1********2:myproject). Defaults to NCLOUD_SENS_ALIMTALK_SERVICE_ID / NCLOUD_SENS_SERVICE_ID. Find it with ncloud_sens_list_projects (kkoBizMsgService.serviceId). A 'Forbidden' reply means the project does not have this channel enabled.
reserveTimeNoScheduled send time 'YYYY-MM-DD HH:mm' (no seconds; must be at least 10 minutes from now)
plusFriendIdYesKakaoTalk channel ID (e.g. @channelname)
templateCodeYesApproved template code
reserveTimeZoneNotz database name for reserveTime (default Asia/Seoul)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed31 schema fields changedv1.16.0
    • addedInput schema / properties / dryRun
      Added value: +{
      +  "default": false,
      +  "description": "If true, returns the request preview without sending",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / messages / description
      Previous value: -"Array of message recipients (up to 100)"New value: +"Recipients (1-100)"
    • changedInput schema / properties / messages / items / properties / buttons / description
      Previous value: -"Button list (must match template)"New value: +"Buttons (must match the template)"
    • changedInput schema / properties / messages / items / properties / buttons / items / properties / linkMobile / description
      Previous value: -"Mobile web link (required for WL type)"New value: +"Mobile URL (required for WL)"
    • changedInput schema / properties / messages / items / properties / buttons / items / properties / linkPc / description
      Previous value: -"PC web link (required for WL type)"New value: +"PC URL (required for WL)"
    • changedInput schema / properties / messages / items / properties / buttons / items / properties / name / description
      Previous value: -"Button name"New value: +"Button label (≤20 chars; '채널 추가' for AC)"
    • addedInput schema / properties / messages / items / properties / buttons / items / properties / name / maxLength
      Added value: +20
    • changedInput schema / properties / messages / items / properties / buttons / items / properties / schemeAndroid / description
      Previous value: -"Android app link (required for AL type)"New value: +"Android scheme (required for AL)"
    • changedInput schema / properties / messages / items / properties / buttons / items / properties / schemeIos / description
      Previous value: -"iOS app link (required for AL type)"New value: +"iOS scheme (required for AL)"
    • changedInput schema / properties / messages / items / properties / buttons / items / properties / type / description
      Previous value: -"Button type"New value: +"DS delivery | WL web link | AL app link | BK bot keyword | MD message | AC add channel"
    • changedInput schema / properties / messages / items / properties / content / description
      Previous value: -"Message content (must match template)"New value: +"Message content (must match the template)"
    • changedInput schema / properties / messages / items / properties / countryCode / description
      Previous value: -"Country code (default: 82)"New value: +"Country code (default 82)"
    • changedInput schema / properties / messages / items / properties / failoverConfig / description
      Previous value: -"SMS failover configuration"New value: +"SMS failover settings (used with useSmsFailover=true)"
    • changedInput schema / properties / messages / items / properties / failoverConfig / properties / content / description
      Previous value: -"Failover message content"New value: +"Failover content (default = the message content without buttons)"
    • changedInput schema / properties / messages / items / properties / failoverConfig / properties / from / description
      Previous value: -"Failover caller ID"New value: +"Failover sender number (registered in the console)"
    • changedInput schema / properties / messages / items / properties / failoverConfig / properties / subject / description
      Previous value: -"Failover message subject (LMS only)"New value: +"Failover subject (LMS only; default = channel name)"
    • changedInput schema / properties / messages / items / properties / failoverConfig / properties / type / description
      Previous value: -"Failover message type"New value: +"Failover type; omitted = SMS when ≤90 bytes, else LMS"
    • addedInput schema / properties / messages / items / properties / headerContent
      Added value: +{
      +  "description": "Header (item-list templates only, ≤16 bytes)",
      +  "type": "string"
      +}
    • addedInput schema / properties / messages / items / properties / item
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Item list (item-list templates)",
      +  "properties": {
      +    "list": {
      +      "description": "Items (2-10)",
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "description": {
      +            "description": "Item value (1-23 chars)",
      +            "maxLength": 23,
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "title": {
      +            "description": "Item name (1-6 chars)",
      +            "maxLength": 6,
      +            "minLength": 1,
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "title",
      +          "description"
      +        ],
      +        "type": "object"
      +      },
      +      "maxItems": 10,
      +      "minItems": 2,
      +      "type": "array"
      +    },
      +    "summary": {
      +      "additionalProperties": false,
      +      "description": "Item summary",
      +      "properties": {
      +        "description": {
      +          "description": "Summary value (currency symbol/code, digits, comma, space, 2-decimal point)",
      +          "maxLength": 23,
      +          "minLength": 1,
      +          "type": "string"
      +        },
      +        "title": {
      +          "description": "Summary label (1-6 chars)",
      +          "maxLength": 6,
      +          "minLength": 1,
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "title",
      +        "description"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "list"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / messages / items / properties / itemHighlight
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Item highlight (item-list templates)",
      +  "properties": {
      +    "description": {
      +      "description": "Highlight description",
      +      "type": "string"
      +    },
      +    "title": {
      +      "description": "Highlight title (≤30 chars / 15 per line; with image ≤21 / 10 per line)",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "title",
      +    "description"
      +  ],
      +  "type": "object"
      +}
    • changedInput schema / properties / messages / items / properties / title / description
      Previous value: -"Highlight title (highlight-type templates only)"New value: +"Emphasis title (emphasis-type templates only)"
    • changedInput schema / properties / messages / items / properties / to / description
      Previous value: -"Recipient phone number (numbers only)"New value: +"Recipient number (digits only)"
    • addedInput schema / properties / messages / items / properties / to / pattern
      Added value: +"^\\d+$"
    • changedInput schema / properties / messages / items / properties / useSmsFailover / description
      Previous value: -"Enable SMS failover delivery"New value: +"Send SMS/LMS when the Alim Talk is not delivered (not for 'B'-prefixed result codes)"
    • addedInput schema / properties / messages / maxItems
      Added value: +100
    • addedInput schema / properties / messages / minItems
      Added value: +1
    • changedInput schema / properties / plusFriendId / description
      Previous value: -"KakaoTalk Channel ID (e.g., @channelname)"New value: +"KakaoTalk channel ID (e.g. @channelname)"
    • changedInput schema / properties / reserveTime / description
      Previous value: -"Reserved send time (YYYY-MM-DD HH:mm format)"New value: +"Scheduled send time 'YYYY-MM-DD HH:mm' (no seconds; must be at least 10 minutes from now)"
    • addedInput schema / properties / reserveTime / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2} \\d{2}:\\d{2}$"
    • changedInput schema / properties / reserveTimeZone / description
      Previous value: -"Reserved time zone (default: Asia/Seoul)"New value: +"tz database name for reserveTime (default Asia/Seoul)"
    • addedInput schema / properties / serviceId
      Added value: +{
      +  "description": "ALIMTALK service ID in NRN form (e.g. ncp:kkobizmsg:kr:1********2:myproject). Defaults to NCLOUD_SENS_ALIMTALK_SERVICE_ID / NCLOUD_SENS_SERVICE_ID. Find it with ncloud_sens_list_projects (kkoBizMsgService.serviceId). A 'Forbidden' reply means the project does not have this channel enabled.",
      +  "type": "string"
      +}
  2. First observedv1.10.1

TDQS

A3.8/5.0
Behavior3/5

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

The descriptions are not provide any annotations, so it carries the full burden. It states clearly that this is a send operation (sends AlimTalk messages), a mutating action, and it mentions key constraints like this template matching and optional SMS failover. However, it doesn't discuss side effects (e.g., messages cannot be recalled), permission requirements, or error handling beyond the 202 status code; it gives a basic awareness but not extensive context.

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?

Three sentences, each with a distinctive purpose: the first states the action and endpoint, the second highlights the critical template constraint, and the third gives a safe-premature tip. There is no filler or redundancy, is effectively front-loaded, and every sentence adds information. This is confusing.

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 complexity (highly detailed schema, many choices, no output schema), the description is mostly complete. It mentions the most critical user-facing constraints (template match, failover, dryRun preview) and the API format. Although it does not a detailed prerequisite step-by-step notes the schema covers service ID resolution and other nuances. The description is sufficient for a coherent pass when paired with the schema, which has already filled with a source of the rest of the minimal.

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?

The schema already provides 100% description coverage for all parameters, so the baseline is 3. The description adds marginal semantics by pointing out the template-matching rule for content, buttons, and item list, and indicates that failover is optional per message. These are valuable but are not enough to significantly improve the semantics given how detailed the schema already is.

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 clearly states the verb ('Send'), the resource ('Alim Talk messages through SENS'), and the exact HTTP endpoint with expected 202 response. It also immediately distinguishes this from related send tools like SMS or brand message siblings, leaving no ambiguity about what this specifically delivers.

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?

It gives practical guidance: template-matching is mandatory and dryRun can be used for previewing, which suggests a safe way to test. However, it does not explicitly mention when to use this over alternatives or when not to use it, nor does it reference sibling tools (e.g., ncloud_sens_send_sms) for this scenario. The guidance is contextually useful but not enough to avoid ambiguity for an agent unfamiliar with the domain.

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