Skip to main content
Glama
Sign In
jade-mcp

jade-mcp

by choiyounggi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

월 근태 달력

jade_calendar
Read-only

Retrieve a month's daily work types, actual work times, and calendar markers such as annual leave for JADE attendance; read-only and saves no records.

Instructions

JADE 「근태현황」 달력에서 한 달의 날짜별 근무유형·실제 근무시각과 날짜 칸 표시(연차휴가 등)를 조회한다. 저장하지 않는다.

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": {
      "month": "<month>"
    },
    "name": "jade_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthYes조회 월 YYYYMM

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with '저장하지 않는다', which is consistent if slightly redundant. The openWorldHint=true live-fetch nature of the JADE system is not disclosed, and no failure modes (e.g. dates with no record) are described, so added value beyond annotations is modest.

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?

Two compact sentences with the resource and returned fields front-loaded, and the no-write caveat placed last where it belongs. No filler, though the save caveat partly duplicates the readOnly annotation.

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 no output schema, the description usefully names the returned data (work type, actual clock times, calendar cell markers). For a one-parameter read tool this is close to sufficient; only the live-system behavior and empty-day handling are unstated.

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 month parameter already documents the YYYYMM format and pattern. The description only restates the one-month scope ('한 달의'), adding no format or edge-case guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (조회한다) and resource (JADE 「근태현황」 달력의 한 달) and enumerates what the output contains: per-date 근무유형, 실제 근무시각, and cell markers such as 연차휴가. The monthly scope implicitly separates it from single-day siblings like jade_today, but no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The monthly scope and the '저장하지 않는다' caveat imply this is the read-only calendar view, but the description never states when to choose it over jade_today or jade_vacation_balance, nor any prerequisites. Usage must be inferred from the field list.

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