Skip to main content
Glama
Sign In
jade-mcp

jade-mcp

by choiyounggi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

연장근무 취소 신청 상신

jade_commit_overtime_cancel
Destructive

Submits a prepared overtime cancellation request to the approval line, rechecking that it remains cancellable and sending only after explicit user preview approval.

Instructions

jade_prepare_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": {
      "token": "<token>"
    },
    "name": "jade_commit_overtime_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesjade_prepare_overtime_cancel 이 돌려준 토큰

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructive=true, idempotent=false and openWorld=true; the description goes further by disclosing the runtime re-validation step (re-querying the target list and aborting if the request is no longer cancellable) and the human-approval gate. That is meaningful behavior beyond what the annotations encode, including a guard against stale tokens.

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?

Three short sentences, each doing distinct work: what it does and with which token, the pre-submit revalidation, and the human-approval requirement. The most safety-critical constraint (direct delivery to the approver) is front-loaded in the final sentence with no filler.

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 single-parameter, destructive, non-idempotent submit tool with no output schema, the description covers the source of the input, the internal revalidation guard, and the user-consent gate. An agent has everything needed to decide whether calling is safe without additional documentation.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already explains that token is the value returned by jade_prepare_overtime_cancel. The description restates that origin but adds no format, expiry, or error-handling detail beyond it, so it meets the baseline rather than exceeding it.

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: submits an overtime-work cancellation request to the approval line (결재선에 상신한다). It also names the sibling that produces the required token, jade_prepare_overtime_cancel, so an agent can distinguish it from the prepare step and from jade_prepare_attendance_cancel without opening any 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?

Gives explicit preconditions: the token must come from jade_prepare_overtime_cancel, the request must still be cancellable at re-query time, and the user must have seen a preview and explicitly approved. It also states the consequence of misuse (the request goes straight to the approver), which is exactly the when-to-call guidance an agent needs for an irreversible submit.

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