Skip to main content
Glama

캘린더 항목 생성

generate_calendar_items
Read-onlyIdempotent

Generates calendar items from real estate transaction timelines, including key dates for contract, move-in, closing, and lease end based on user role and transaction type.

Instructions

타임라인을 캘린더 입력용 항목으로 변환합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stageNo문서 또는 단계 구분.
regionNo시/군/구 수준까지만 허용. 상세주소 금지.
contextNo전문가 검토 트리거용 문맥 태그.
user_roleYes사용자 역할. buyer 또는 tenant.
closing_dateNoYYYY-MM-DD 형식의 잔금일.
current_dateNoYYYY-MM-DD 형식의 기준일.
move_in_dateNoYYYY-MM-DD 형식의 입주일.
contract_dateNoYYYY-MM-DD 형식의 계약일.
calendar_styleNo캘린더 출력 스타일.
lease_end_dateNoYYYY-MM-DD 형식의 임대차 종료일.
transaction_typeYes거래 유형. home_purchase, lease_jeonse, lease_monthly 중 하나.
deposit_amount_rangeNo정확한 액수 대신 범위 문자열.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
dataNo
errorNo
unknownsYes
disclaimerYes
expert_review_pointsYes
source_status_summaryYes
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating no side effects. The description 'converts' aligns with a transformation operation but adds no extra behavioral context. No contradictions found.

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?

The description is a single sentence with no wasted words. However, it is very brief and could benefit from more detail without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having 12 parameters and an output schema, the description is minimal. It does not explain what constitutes a timeline or how the conversion works. The context of calendar items and the input format is insufficient for confident usage.

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?

All 12 parameters are described in the schema (100% coverage). The description adds no additional parameter-level meaning beyond what the schema already provides.

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?

The description states the tool converts a timeline into calendar items, providing a clear verb and resource. However, it does not differentiate from siblings like generate_post_contract_timeline or generate_required_documents, which have distinct purposes.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives, nor are there any prerequisites or exclusions. The description only states what it does, not the context of use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/inhoinno86-hub/kakao_mcp_checktime'

If you have feedback or need assistance with the MCP directory API, please join our Discord server