Skip to main content
Glama
Sign In
jade-mcp

jade-mcp

by choiyounggi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

재택근무 신청 준비 (지정 날짜)

jade_prepare_remote_work_day
Read-only

Prepare a JADE remote work application for a specified date up to submission, run closing checks, and return a preview with a one-time token without submitting it.

Instructions

지정한 하루의 JADE 재택 근무 신청서를 상신 직전까지 채우고 마감 검사를 통과시킨 뒤 미리보기와 일회용 토큰을 돌려준다. 상신하지 않는다. 결재 대기 중인 같은 날 신청은 달력에 안 보여 두 번 상신될 수 있으므로, 먼저 jade_applications(statuses=[approving])로 그날 재택 신청이 없는지 확인한다. 사유 기본값은 「M월 D일 재택근무 신청드립니다.」. 사용자가 미리보기를 확인하고 승인한 뒤에만 jade_commit_remote_work 로 상신한다.

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

Input Schema

NameRequiredDescriptionDefault
dateYes재택 날짜 YYYYMMDD
reasonNo신청 사유

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, and the description is consistent: nothing is submitted, only a prepared payload plus token is produced. Beyond the annotations it discloses the deadline-check step, the duplicate-submission hazard for approving-status applications that don't show on the calendar, and the default reason string; the only remaining gap is that the one-time token's lifetime/scope is not spelled out.

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 what the tool does and the crucial "does not submit" statement, followed by the duplicate-check warning and the commit hand-off. Every sentence earns its place; the only minor redundancy is restating non-submission implicitly through the token/commit sequence.

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 two return artifacts (preview and one-time token). For a two-parameter prepare tool in a prepare/commit pair, an agent has everything needed: prerequisite check, default value, safety profile, and the required follow-up tool.

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% and both parameters are documented, so the schema carries the baseline. The description still adds value by supplying the default reason text (「M월 D일 재택근무 신청드립니다.」) and by framing `date` as a single day rather than a range, which the schema does not say.

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+resource+scope: it fills the JADE remote-work application for one specified day up to the point just before submission, then returns a preview and a one-time token. It explicitly names what it does NOT do ("상신하지 않는다") and thereby separates itself from the commit sibling, and the "지정한 하루" wording distinguishes it from the range-based jade_prepare_remote_work.

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 an explicit pre-condition (first verify with jade_applications(statuses=[approving]) that no same-day remote-work application is pending) and an explicit post-condition (only after the user reviews the preview and approves, submit via jade_commit_remote_work). Both the when-to-use and the hand-off alternative are named, leaving nothing to inference.

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