Skip to main content
Glama
Sign In
jade-mcp

jade-mcp

by choiyounggi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

생일반차 신청 상신

jade_commit_condolence
Destructive

Submits a prepared birthday half-day or condolence leave request to the approval line using the token from jade_prepare_condolence, only after the user reviews and explicitly approves the preview.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
tokenYesjade_prepare_condolence 가 돌려준 토큰

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?

Annotations already declare this is not read-only, is destructive, open-world, and non-idempotent. The description adds important workflow context beyond the annotations: the submission goes directly to the approver and requires prior preview and explicit user approval.

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?

Two sentences, with the action and prerequisite stated first, followed by the safety condition. There is no redundant wording.

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?

For a one-parameter destructive commit tool with annotations covering the safety profile, the description provides the essential prerequisite and approval gate. It does not describe the return or failure behavior, but no output schema exists and the core invocation requirements are covered.

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?

There is only one parameter, token, and schema coverage is 100%, so the schema already documents that it comes from jade_prepare_condolence. The description reinforces that meaning but adds no further syntax or format details beyond the schema.

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 states a specific verb, 상신 (submit to approval line), and a specific resource, 생일반차/경조 휴가 신청서, using a token from jade_prepare_condolence. It clearly distinguishes this commit action from the corresponding prepare sibling.

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 prerequisite, the token from jade_prepare_condolence, and an explicit usage condition: call only after the user has seen the preview and approved. It does not enumerate alternatives beyond the prepare step, but the context is clear enough to guide invocation.

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