Skip to main content
Glama
Sign In
jade-mcp

jade-mcp

by choiyounggi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

생일반차 신청 준비

jade_prepare_condolence
Read-only

Prepares a JADE birthday half-day leave request up to submission, validates it on the server, and returns a preview and one-time token without submitting it.

Instructions

JADE 경조 휴가 신청서로 생일반차를 상신 직전까지 채우고 서버 검증을 통과시킨 뒤 미리보기와 일회용 토큰을 돌려준다. 상신하지 않는다. 결혼·출산·조사 등 다른 경조 유형은 쓰지 않는다. 사용자가 미리보기를 확인하고 승인한 뒤에만 jade_commit_condolence 로 상신한다.

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": {
      "conType": "<conType>",
      "date": "<date>"
    },
    "name": "jade_prepare_condolence"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes반차 쓰는 날 YYYYMMDD
reasonNo신청 사유생일 반차
conTypeYes3010=생일반차 오후, 3020=생일반차 오전

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 real context beyond them – server-side validation must pass, the call returns a preview and a single-use token, and nothing is submitted. It stays consistent with readOnlyHint because no submission occurs. It stops short of stating what happens when validation fails or how long the token lives, which are the remaining gaps for a prepare/commit pair.

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 with zero filler: purpose first, then the non-submission guarantee, then the type exclusion, then the commit handoff. Each sentence carries a distinct decision-relevant fact.

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?

There is no output schema, and the description compensates by naming the return values (preview and one-time token) and by framing the two-step prepare/commit workflow. For a 3-parameter preparation tool with annotations covering safety, an agent has everything needed to call it correctly and to know what follows.

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 the enum meanings (3010=afternoon, 3020=morning) plus the YYYYMMDD pattern are already documented in the schema. The description adds no syntax, default, or edge-case guidance for date/conType/reason beyond what the schema provides, so the baseline 3 applies.

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 uses a specific verb and resource: it fills a JADE condolence-leave form for a birthday half-day up to the point just before submission, runs server validation, and returns a preview plus a one-time token. It explicitly disclaims other condolence types (marriage, birth, investigation) and names jade_commit_condolence as the separate submit step, so an agent can distinguish it from all ~30 siblings without opening a 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?

It states the exclusion ('다른 경조 유형은 쓰지 않는다'), the terminal condition ('상신하지 않는다'), and the handoff rule: only after the user reviews the preview and approves should jade_commit_condolence be called. That is an explicit when/when-not plus a named alternative.

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