Skip to main content
Glama
Sign In
jade-mcp

jade-mcp

by choiyounggi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

재택근무 취소 신청 준비 (한 날)

jade_prepare_remote_work_revert
Read-only

Prepares a remote-work cancellation request for a chosen date and work type, validates it, and returns a preview plus one-time token for later submission without submitting it.

Instructions

재택근무제로 바뀐 날을 재택 근무 신청서로 사용자가 고른 근무유형으로 되돌리는 신청서를 상신 직전까지 채우고 마감 검사를 통과시킨 뒤 미리보기와 일회용 토큰을 돌려준다. 상신하지 않는다. 그날이 아직 재택근무제가 아니면(결재 대기 포함) 막는다. 사유 기본값은 「M월 D일 재택근무 취소 신청드립니다.」. 사용자가 미리보기를 확인하고 승인한 뒤에만 jade_commit_remote_work_revert 로 상신한다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>",
      "workType": "<workType>"
    },
    "name": "jade_prepare_remote_work_revert"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes재택을 취소할 날 YYYYMMDD
reasonNo신청 사유
workTypeYes되돌릴 근무유형 이름 (예: 선택근무제(IT)). 원래 근무유형은 미리보기로 확인할 수 없으므로 사용자에게 받는다

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Beyond readOnlyHint=true and openWorldHint=true, the description discloses the most important behavioral trait: this tool does not submit (상신하지 않는다). It also states the return payload (미리보기 + 일회용 토큰), the blocking condition, and the default reason value. It is consistent with readOnlyHint=true: the tool prepares and validates but does not write. It does not state what the one-time token's lifetime or reuse rules are, which is the only remaining gap.

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?

The description front-loads the core action, then constraints, then the handoff to the commit tool, with no redundant sentences. However, it is one very dense run-on paragraph, and the ordering of the blocking rule after the return-value sentence makes it slightly harder to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter prepare tool with no output schema, the description covers everything an agent needs: the side-effect boundary, the return payload, the failure condition, the default value, and the required next tool. No output schema exists, but the description names the two return values, so the gap is closed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the schema documents date, reason, and workType. The description adds meaning the schema does not: the default reason text 「M월 D일 재택근무 취소 신청드립니다.」, and why workType must come from the user (the original work type cannot be recovered from the preview, so it cannot be inferred).

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 chain and resource: it fills a revert application up to the point just before submission (상신 직전), passes a closing validation check, and returns a preview plus a one-time token. It distinguishes itself from jade_commit_remote_work_revert, which performs the actual submission, and from jade_prepare_remote_work (the opposite direction).

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

Usage Guidelines5/5

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

It gives the exact usage sequence: the user must review the preview and approve it before jade_commit_remote_work_revert is called. It also states a hard precondition: if the day is not yet 재택근무제 (including while 결재 is pending), the request is blocked. That covers when to use, when not to use, and which alternative to call next.

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