Skip to main content
Glama
SihyeonJeon

legend-saju

by SihyeonJeon

Select auspicious dates

legend_saju_select_dates
Read-only

Pick auspicious dates for major events such as moving, opening a business, or surgery by comparing your birth details against a target date range. Delivers structured Saju evidence for each option.

Instructions

Use this only when the user explicitly asks for 택일, 좋은 날, 계약일, 이사일, 개업일, 수술일, or another date-selection task. Do not use it merely because a fortune request mentions this year.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
birthYes
purposeNo
questionYesThe event and constraints for choosing a date.
maxClaimsNoMaximum interpretation points and raw claims returned outside debug mode.
rangeDaysNo
outputModeNoBackward-compatible developer projection override. Ordinary callers should use detailLevel instead.
targetDateYesStart date for the candidate range.
detailLevelNoPreferred depth. brief is shortest, standard is the default readable answer, expert automatically composes question-relevant deep methods and evidence in one call, and raw is the complete developer record.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo
errorNo
claimsNo
routesNo
blockedNo
dossierNo
sourcesNo
evidenceNo
questionNo
sectionsNo
timelineNo
conflictsNo
selectionNo
inputNotesNo
detailLevelNo
limitationsNo
nameAnalysisNo
noModelCallsNo
dreamAnalysisNo
executionPlanNo
methodAnalysisNo
readingSummaryNo
recommendationsNo
calculationSummaryNo
omittedTimelineYearsNo
interpretationBoundaryNo
publicationSideEffectsNo
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds context about the intended invocation trigger and avoids misapplication, but it does not disclose further behavioral details such as how candidate dates are returned or constrained beyond schema and output schema.

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 no wasted filler, and the most decisive usage rule is stated up front. The Korean examples add practical precision without padding.

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?

Given the rich input schema, output schema, and safety annotations, the description provides the essential missing piece: when the tool should be selected and when it must not be. It is slightly thin on what the returned results represent, but the output schema mitigates that gap.

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?

The description adds no parameter-level meaning; all parameter knowledge is carried by the schema, which covers 63% of parameters. Since the schema already documents some fields like calendar defaults, timezone handling, and hour ambiguity, a baseline 3 is appropriate.

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 clearly defines the tool's scope: it is for date-selection tasks (택일, 좋은 날, 계약일, 이사일, 개업일, 수술일), not for ordinary fortune readings. This specificity distinguishes it from read_fortune and other fortune-related siblings.

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 explicit when-to-use criteria with concrete examples and a clear exclusion ('Do not use it merely because a fortune request mentions this year'). It does not name the alternative sibling tool to use instead, so it is slightly less helpful than it could be.

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/SihyeonJeon/legend-saju'

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