Skip to main content
Glama
Sign In
jade-mcp

jade-mcp

by choiyounggi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

재택근무 신청 준비 (월·요일)

jade_prepare_remote_work
Read-only

Prepare monthly JADE remote-work request forms for a chosen weekday, validate them for submission, and return per-date previews and one-time tokens without submitting.

Instructions

한 달의 지정 요일마다 JADE 재택 근무 신청서를 한 장씩 상신 직전까지 채우고 마감 검사를 통과시킨 뒤, 날짜별 미리보기와 일회용 토큰을 돌려준다. 상신하지 않는다. 그 달의 주는 첫 평일이 든 주부터 평일이 다음 달로 넘어가지 않는 주까지이며, 주중(월~금)에 공휴일이 있거나 휴가 표시가 있는 주, 이미 재택이거나 지난 날짜는 빼고 그 사유를 skipped 로 알려 준다. 1일이 목·금이면 첫 주의 요일이 전달 날짜일 수 있다. 결재 대기 중인 신청은 달력에 안 보일 수 있으니 같은 날을 두 번 상신하지 않게 주의한다. 사유는 「M월 D일 재택근무 신청드립니다.」. 사용자가 미리보기를 확인하고 승인한 뒤에만 날짜마다 jade_commit_remote_work 로 상신한다.

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": {
      "month": "<month>",
      "weekday": "<weekday>"
    },
    "name": "jade_prepare_remote_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthYes신청 월 YYYYMM
weekdayYes재택 요일 mon|tue|wed|thu|fri

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the exclusion rules (weeks containing a Mon–Fri public holiday or vacation marking, already-remote or past dates), that exclusions are reported back as skipped with reasons, and the edge case where the 1st falling on Thu/Fri makes the first week's weekday a prior-month date. It also states the exact reason text that will be written and that the returned tokens are one-time.

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?

Front-loaded with the action and the non-submitting guarantee, then the week-boundary and exclusion rules. It is dense and long, and the no-submit point is effectively restated in the final sentence, but that redundancy is safety-relevant rather than padding.

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 tool with non-trivial calendar logic, two parameters, and no output schema, the description covers the return payload (per-date preview + one-time token), the skipped-date reporting, the reason template, and the handoff to the commit tool. An agent has everything needed to call it and to interpret the result.

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 100%, so the format and enum are already covered by the schema. The description still adds meaning the schema cannot: that the weekday is applied to every qualifying occurrence within a month whose week boundaries follow the stated first-week/last-week rule. That operationalizes the two parameters rather than restating them.

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 first sentence gives a specific verb+resource+scope: fill one JADE remote-work application per designated weekday of a month, run the closing checks, and return per-date previews plus one-time tokens. The explicit "상신하지 않는다" (does not submit) immediately distinguishes it from jade_commit_remote_work.

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?

Explicit when-to-use and when-not: this tool only prepares, and jade_commit_remote_work must be called per date only after the user reviews the preview and approves. It also adds a concrete caution about pending-approval applications not appearing on the calendar and the risk of double-submitting the same day.

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