Skip to main content
Glama
jade-mcp
by choiyounggi

연장근무 취소 신청 준비

jade_prepare_overtime_cancel
Read-only

Prepares a JADE overtime cancellation request up to submission by choosing the correct eligible application for the work date and returning a preview plus one-time token; it does not submit.

Instructions

JADE 연장 근무 취소 신청서를 상신 직전까지 채우고 미리보기와 일회용 토큰을 돌려준다. 상신하지 않는다. 화면의 「취소할 사전근무 선택」 목록을 근무일이 든 달로 조회해 그날의 신청 한 건을 고른다. JADE 가 취소를 막은 신청(취소신청 가능=N)은 고르지 않고, 같은 날 취소할 수 있는 신청이 여러 건이면 startHm 으로 고르게 한다. 사용자가 미리보기를 확인하고 승인한 뒤에만 jade_commit_overtime_cancel 로 상신한다.

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>",
      "reason": "<reason>"
    },
    "name": "jade_prepare_overtime_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes취소할 연장근무의 근무일 YYYYMMDD
reasonYes취소 사유
startHmNo같은 날 여러 건일 때 고를 근무 시작 시각 HHMM

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations only declare readOnlyHint and openWorldHint; the description adds that nothing is submitted, that a preview and single-use token are produced, and that a user approval gate precedes commit — real behavioral context beyond the annotations. It stops short of covering token lifetime, reuse rules, or what the preview contains, so it is strong but not exhaustive.

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 core action and the non-submission disclaimer, then the selection procedure, then the commit handoff — a logical order with no filler. The only redundancy is that '상신하지 않는다' is restated at the end of the final sentence, a minor cost.

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?

With no output schema, the description correctly compensates by describing the returns (preview and one-time token) and the no-submit guarantee, plus the candidate-selection rules. Enough for an agent to call it correctly; missing only details like token lifetime and preview contents.

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 baseline is 3, but the description adds selection semantics the schema lacks: date is used to query the candidate list by workday month, and startHm is specifically the tiebreaker when several cancellable applications share a day. That is meaningfully more than the parameter descriptions provide.

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?

States a specific verb and resource: fills the JADE overtime-cancellation application up to just before submission and returns a preview plus a one-time token. It immediately excludes the commit step, so an agent can distinguish it from jade_commit_overtime_cancel without opening either schema.

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?

Explicitly says to select one application from the '취소할 사전근무 선택' list queried by workday month, to skip applications JADE has blocked (취소신청 가능=N), and to disambiguate multiple same-day applications by startHm. It also states the commit tool is used only after the user reviews and approves the preview, naming the alternative and the condition that selects it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.