Skip to main content
Glama
Sign In
jade-mcp

jade-mcp

by choiyounggi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

근태/근무 취소 신청 준비

jade_prepare_attendance_cancel
Read-only

Prepares an attendance/work cancellation request for a selected original application, checks popup eligibility, and returns a preview plus one-time token for later commit without submitting.

Instructions

jade_attendance_cancel_candidates 로 고른 원신청(applId)의 근태/근무 취소 신청서를 상신 직전까지 채우고, 그 원신청이 팝업에서 고를 수 있는 행인지 확인한 뒤 미리보기와 일회용 토큰을 돌려준다. 상신하지 않는다. 사용자가 미리보기를 확인하고 승인한 뒤에만 jade_commit_attendance_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": {
      "applId": "<applId>",
      "reason": "<reason>"
    },
    "name": "jade_prepare_attendance_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo원신청을 찾을 조회 종료일 YYYYMMDD. 목록 조회 때와 같게
fromNo원신청을 찾을 조회 시작일 YYYYMMDD. 목록 조회 때와 같게
applIdYes취소할 원신청 번호 (목록의 applId)
reasonYes취소 사유

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

readOnlyHint=true is consistent with the description's claim that this only prepares and never submits, and the description adds real behavior beyond annotations: it returns a preview and a single-use token, and it performs a popup-selectability validation on the original application that can fail. It does not cover token lifetime, what the preview contains, or what happens when the popup check fails, so it stops short of full disclosure.

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?

Three compact sentences, front-loaded with what the tool does and immediately followed by the non-submission constraint and the next-step handoff. The first sentence is long and stacks several actions, but no sentence is wasted.

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 takes on the burden of describing returns, and it does name both artifacts (preview and one-time token) and how the token feeds the commit step. What remains unstated — preview contents, token expiry, validation failure behavior — is minor for a prepare-stage read-only tool in a well-populated prepare/commit family.

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 coverage is 100%, so the schema already documents all four parameters, which sets the baseline at 3. The description adds provenance for applId (it must be a value chosen via jade_attendance_cancel_candidates), but adds nothing about the from/to date window or the reason field beyond what the schema states.

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: it fills a cancellation application form for the original application (applId) up to the point just before submission, validates that the original row is selectable in the popup, and returns a preview plus a one-time token. It explicitly names the sibling that supplies applId (jade_attendance_cancel_candidates) and the sibling that finishes the job (jade_commit_attendance_cancel), so it is distinguishable from the prepare/commit pairs around it.

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?

Gives the full selection chain: choose applId from jade_attendance_cancel_candidates, run this to prepare, have the user confirm the preview, then call jade_commit_attendance_cancel. It also states an explicit exclusion — '상신하지 않는다' (does not submit) — so there is no ambiguity about which tool performs the write.

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