Skip to main content
Glama

nworks_calendar_update

Modify existing calendar events in LINE WORKS. Change meeting titles, adjust times, update locations, or edit descriptions using event ID from calendar list.

Instructions

기존 캘린더 일정을 수정합니다. '일정 시간 변경해줘', '회의 제목 바꿔줘' 등의 요청에 사용. User OAuth 인증 필요 (calendar + calendar.read scope). eventId는 nworks_calendar_list로 조회 가능

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventIdYes일정 ID (nworks_calendar_list로 조회 가능)
summaryNo새 제목
startNo새 시작 일시 (YYYY-MM-DDThh:mm:ss)
endNo새 종료 일시 (YYYY-MM-DDThh:mm:ss)
timeZoneNo타임존 (기본: Asia/Seoul)
descriptionNo새 설명
locationNo새 장소
sendNotificationNo참석자에게 알림 발송 (기본: false)
userIdNo대상 사용자 ID (미지정 시 me)

Implementation Reference

  • The handler function for nworks_calendar_update that calls calendarApi.updateEvent.
    async ({
      eventId, summary, start, end, timeZone,
      description, location,
      sendNotification, userId,
    }) => {
      try {
        await calendarApi.updateEvent({
          eventId,
          summary,
          start,
          end,
          timeZone,
          description,
          location,
          sendNotification,
          userId: userId ?? "me",
        });
        return {
          content: [{ type: "text" as const, text: JSON.stringify({ success: true, eventId, message: "일정이 수정되었습니다" }) }],
        };
      } catch (err) {
        return {
          content: [{ type: "text" as const, text: mcpErrorHint(err, "calendar.update") }],
          isError: true,
        };
  • Registration of the nworks_calendar_update tool with Zod schema for input validation.
    server.tool(
      "nworks_calendar_update",
      "기존 캘린더 일정을 수정합니다. '일정 시간 변경해줘', '회의 제목 바꿔줘' 등의 요청에 사용. User OAuth 인증 필요 (calendar + calendar.read scope). eventId는 nworks_calendar_list로 조회 가능",
      {
        eventId: z.string().describe("일정 ID (nworks_calendar_list로 조회 가능)"),
        summary: z.string().optional().describe("새 제목"),
        start: z.string().optional().describe("새 시작 일시 (YYYY-MM-DDThh:mm:ss)"),
        end: z.string().optional().describe("새 종료 일시 (YYYY-MM-DDThh:mm:ss)"),
        timeZone: z.string().optional().describe("타임존 (기본: Asia/Seoul)"),
        description: z.string().optional().describe("새 설명"),
        location: z.string().optional().describe("새 장소"),
        sendNotification: z.boolean().optional().describe("참석자에게 알림 발송 (기본: false)"),
        userId: z.string().optional().describe("대상 사용자 ID (미지정 시 me)"),
      },
Behavior3/5

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

Without annotations, the description carries the full burden and discloses auth requirements (OAuth with specific scopes) and workflow dependencies (must list before updating). However, it omits critical behavioral details: whether updates are partial (PATCH) or full replacement, what happens if the eventId is invalid, and whether the operation is idempotent.

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?

Extremely efficient structure: purpose statement, usage examples, auth requirements, and parameter lookup instruction. Each sentence earns its place with no redundancy or filler. Information is front-loaded with the core action ('기존 캘린더 일정을 수정합니다') presented first.

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?

For a 9-parameter mutation tool with no annotations and no output schema, the description adequately covers the authentication barrier and lookup workflow. However, it lacks operational context expected for a destructive/mutating operation: no mention of partial vs. complete updates, error scenarios, or side effects beyond the sendNotification parameter.

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%, establishing a baseline of 3. The description mentions that eventId is available via nworks_calendar_list, but this merely duplicates the schema's own description for that field. No additional semantic context (e.g., date format examples, timezone handling beyond the default) is provided beyond what the schema already documents.

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 clearly states it modifies '기존 캘린더 일정' (existing calendar events) using the specific verb '수정합니다' (modifies). It implicitly distinguishes from sibling tools like nworks_calendar_create by emphasizing 'existing' events and referencing nworks_calendar_list for lookup, though it doesn't explicitly contrast with delete or create operations.

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?

Provides concrete usage examples ('일정 시간 변경해줘', '회의 제목 바꿔줘') showing when to use the tool. Documents prerequisites including OAuth scope requirements (calendar + calendar.read) and the dependency on nworks_calendar_list to obtain eventId. Lacks 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/yjcho9317/nworks'

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