Skip to main content
Glama
Sign In
jade-mcp

jade-mcp

by choiyounggi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

근태/근무 취소 대상 조회

jade_attendance_cancel_candidates
Read-only

Retrieve original attendance, leave, and business-trip entries for a cancellation request, showing selectable status and blocked reasons so users know which requests can be canceled.

Instructions

JADE 근태/근무 취소 신청서의 「취소할 근태/휴가 선택」 팝업이 보여 주는 원신청 목록(출장·근태 등)을 조회한다. 저장하지 않는다. selectable=false 인 행은 취소 신청을 올릴 수 없고 blockedReason 에 이유가 있다. 재택근무 취소는 이 목록에 나오지 않으므로 jade_prepare_remote_work_revert 를 쓴다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jade_attendance_cancel_candidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo조회 종료일 YYYYMMDD. 없으면 이번 달 말일
fromNo조회 시작일 YYYYMMDD. 없으면 이번 달 1일

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, and the description reinforces that with '저장하지 않는다'. Beyond the annotations it adds genuinely useful behavioral detail: rows with selectable=false cannot be submitted for cancellation and carry the reason in blockedReason. It doesn't describe the remaining row fields or whether the result is paginated, which keeps it from a 5.

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?

Four short sentences, front-loaded with the identity of the tool, then the no-save guarantee, then the row semantics, then the exclusion. Nothing is redundant and the alternative is placed last where it belongs.

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 carries the burden of explaining return values, and it does cover the two structurally important ones (selectable, blockedReason). It is not fully complete because the rest of the row shape and the default date window are left to the schema.

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% and both from/to parameters are already documented with formats and defaults in the schema, so a baseline 3 applies. The description adds no date-syntax or range semantics 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?

The description pairs a specific verb (조회한다, list/query) with a specific resource (the original application list shown in the 「취소할 근태/휴가 선택」 popup of the JADE attendance/work cancellation form). It also draws a clear boundary against the sibling jade_prepare_remote_work_revert, so an agent can distinguish it 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 Guidelines4/5

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

It gives an explicit exclusion: remote-work cancellation does not appear in this list and must go through jade_prepare_remote_work_revert instead. That is real routing guidance, but it doesn't explicitly state that this tool is the read step preceding jade_prepare_attendance_cancel, so the positive when-to-use link is only implied by the form-popup framing.

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