Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_sens_list_alimtalk_templates

Read-only

List AlimTalk templates by channel ID, with optional template code or name filters. Retrieve full details, including inspection comments, and control results via pagination.

Instructions

List Alim Talk templates of a channel (GET /alimtalk/v2/services/{serviceId}/templates). channelId is required; giving templateCode returns that template's full detail including inspection comments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageSizeNoItems per page (1-100, default 100)
channelIdYesKakaoTalk channel ID (e.g. @channelname, from ncloud_sens_list_alimtalk_channels)
pageIndexNoPage index (0-based, default 0)
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.
templateCodeNoTemplate code → detailed view
templateNameNoFilter by name (full or partial match)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.16.0
    • changedInput schema / properties / channelId / description
      Previous value: -"KakaoTalk Channel ID (e.g., @channelname)"New value: +"KakaoTalk channel ID (e.g. @channelname, from ncloud_sens_list_alimtalk_channels)"
    • changedInput schema / properties / pageIndex / description
      Previous value: -"Page index (0-N, default: 0)"New value: +"Page index (0-based, default 0)"
    • addedInput schema / properties / pageIndex / minimum
      Added value: +0
    • changedInput schema / properties / pageIndex / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / pageSize / description
      Previous value: -"Number of items per page (1-100, default: 100)"New value: +"Items per page (1-100, default 100)"
    • addedInput schema / properties / pageSize / maximum
      Added value: +100
    • addedInput schema / properties / pageSize / minimum
      Added value: +1
    • changedInput schema / properties / pageSize / type
      Previous value: -"number"New value: +"integer"
    • 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"
+}
    • changedInput schema / properties / templateCode / description
      Previous value: -"Template code (if provided, returns template details including inspection info)"New value: +"Template code → detailed view"
    • changedInput schema / properties / templateName / description
      Previous value: -"Template name filter (partial match)"New value: +"Filter by name (full or partial match)"
  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?

The readOnlyHint annotation already establishes this as a safe read operation, so the burden on the description is lower. The description adds useful behavioral context beyond the annotation: it names the HTTP method (GET), requires channelId, and discloses that providing templateCode returns full detail including inspection comments. No contradictions or hidden side effects are suggested.

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 two tight sentences that front-load the core purpose and endpoint, then add the key behavioral distinction for templateCode. Every clause earns its place and there is no filler or redundancy.

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?

For a read-only list tool with a 100%-documented schema, the description plus schema cover what an agent needs: the channel scope, the detail mode, pagination parameters, and even hints for resolving channelId and serviceId. There is no output schema, so return shape is not spelled out, but this is a minor gap for a simple list operation.

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 six parameters thoroughly. The description's parameter-related statements ('channelId is required', 'templateCode returns full detail') mostly restate what the schema already says. It adds no significant parameter semantics beyond the input schema.

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 states a specific verb and resource ('List Alim Talk templates of a channel') and includes the exact REST endpoint, making the tool's purpose unambiguous. It clearly distinguishes this from sibling tools like ncloud_sens_list_alimtalk_channels and ncloud_sens_list_alimtalk_requests. The added note about templateCode providing full detail further sharpens what this tool does.

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 gives clear context: this tool lists templates for a channel, and the condition 'giving templateCode returns that template's full detail' provides actionable usage guidance. It does not explicitly name alternatives or state when not to use it, but the endpoint and required channelId make the intended scenario clear.

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