Skip to main content
Glama
Sign In
jade-mcp

jade-mcp

by choiyounggi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

출근/퇴근 기록 준비

jade_prepare_punch
Read-only

Validates and previews a JADE clock-in or clock-out punch before saving, returning a one-time token; no record is stored until user approval.

Instructions

JADE 출근(in) 또는 퇴근(out) 기록을 저장 직전까지 검증하고 미리보기와 일회용 토큰을 돌려준다. 저장하지 않는다. 사용자가 미리보기를 확인하고 승인한 뒤에만 jade_commit_punch 로 저장한다.

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": {
      "kind": "<kind>"
    },
    "name": "jade_prepare_punch"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesin=출근, out=퇴근

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description is consistent with that by stating it does not save. Beyond the annotations it discloses the return payload (a preview plus a one-time token) and the human-approval gate, though it does not describe token lifetime, failure modes, or what the preview contains.

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, front-loaded with the core action and the non-persistence guarantee, then the commit handoff. No filler or redundant restatement of the title.

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 only one enum parameter and no output schema, the description covers what an agent needs: that nothing is saved, that a preview and token come back, and that jade_commit_punch is the follow-up. Minor gap in not explaining how the token is passed to the commit call or how long it stays valid.

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 single parameter is an enum already documented as in=출근, out=퇴근. The description restates the in/out meaning but adds no format or constraint detail beyond the schema, so the baseline of 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 names a specific verb (validate/prepare up to just before saving) and resource (JADE clock-in/out punch record), and explicitly states it does not persist. It also distinguishes itself from the sibling jade_commit_punch by naming that tool as the saving step.

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 exactly when to use this tool (to obtain a preview and one-time token) and when to use the alternative (jade_commit_punch, only after the user reviews and approves the preview). The two-step prepare/commit workflow is spelled out rather than left 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