Skip to main content
Glama
yolstudio26-oss

Saroday MCP Server

lookup_glossary

Look up definitions of over 80 Myeongni-hak terms including Saju elements like Cheon-eok Gwiyi, Dohwasal, and Yookhap. Get precise explanations for Saju glossary terms.

Instructions

명리학 용어 풀이 조회. 십성(비견·겁재·식신·상관·편재·정재·편관·정관·편인·정인), 신살(천을귀인·도화살·역마살·양인살·괴강살 등 28+ 종류), 합충형파해(천간합/충, 육합·삼합·반합·방합, 충/형/파/해/원진), 12운성(장생·목욕·관대·건록·제왕·쇠·병·사·묘·절·태·양) 등 80+개 용어 풀이를 반환합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYes조회할 명리학 용어 (한글). 예: '도화살', '식신', '천을귀인', '육합', '제왕'

Implementation Reference

  • The main handler function for the 'lookup_glossary' tool. It takes a 'term' argument, calls the Saroday API at /api/v1/glossary/{term}, and formats the response with term details, Hanja, classification, summary, meaning, positive/negative aspects, effect, and tips.
    async function handleLookupGlossary(args) {
      const term = encodeURIComponent(String(args.term || "").trim());
      if (!term) {
        return {
          isError: true,
          content: [{ type: "text", text: "Error: 'term' parameter is required." }],
        };
      }
    
      const { body } = await callSarodayAPI(`/api/v1/glossary/${term}`);
      const d = body.data;
    
      let text = `# ${d.term}${d.hanja ? ` (${d.hanja})` : ""}\n`;
      text += `**분류:** ${d.type}${d.category ? ` · ${d.category}` : ""}\n\n`;
      if (d.summary)  text += `**요약:** ${d.summary}\n\n`;
      if (d.meaning)  text += `**의미:** ${d.meaning}\n\n`;
      if (d.positive) text += `**긍정 측면:** ${d.positive}\n\n`;
      if (d.negative) text += `**주의 사항:** ${d.negative}\n\n`;
      if (d.effect)   text += `**작용:** ${d.effect}\n\n`;
      if (d.tip)      text += `**활용 팁:** ${d.tip}\n`;
    
      return { content: [{ type: "text", text }] };
    }
  • The tool definition and input schema for 'lookup_glossary'. Defines the tool name, description in Korean, and inputSchema requiring a single 'term' string parameter.
    {
      name: "lookup_glossary",
      description:
        "명리학 용어 풀이 조회. 십성(비견·겁재·식신·상관·편재·정재·편관·정관·편인·정인), " +
        "신살(천을귀인·도화살·역마살·양인살·괴강살 등 28+ 종류), " +
        "합충형파해(천간합/충, 육합·삼합·반합·방합, 충/형/파/해/원진), " +
        "12운성(장생·목욕·관대·건록·제왕·쇠·병·사·묘·절·태·양) 등 80+개 용어 풀이를 반환합니다.",
      inputSchema: {
        type: "object",
        properties: {
          term: {
            type: "string",
            description: "조회할 명리학 용어 (한글). 예: '도화살', '식신', '천을귀인', '육합', '제왕'",
          },
        },
        required: ["term"],
      },
    },
  • index.js:376-377 (registration)
    The dispatch/call routing that maps the tool name 'lookup_glossary' to the handleLookupGlossary handler function in the CallToolRequestSchema handler.
    case "lookup_glossary":
      return await handleLookupGlossary(args);
  • index.js:365-367 (registration)
    The ListToolsRequestSchema handler that registers all tools (including lookup_glossary) from the TOOLS array.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
  • The callSarodayAPI helper function used by handleLookupGlossary to make HTTP requests to the Saroday API.
    async function callSarodayAPI(path, options = {}) {
      const url = `${API_BASE}${path}`;
      const startedAt = Date.now();
    
      try {
        const res = await fetch(url, {
          ...options,
          headers: {
            "User-Agent": USER_AGENT,
            "Accept": "application/json",
            ...(options.headers || {}),
          },
        });
    
        const elapsedMs = Date.now() - startedAt;
        const text = await res.text();
        let body;
        try {
          body = JSON.parse(text);
        } catch (_) {
          body = { raw: text };
        }
    
        if (!res.ok) {
          const errMsg = (body && body.error && body.error.message) || `HTTP ${res.status}`;
          throw new Error(`Saroday API error (${res.status}): ${errMsg}`);
        }
    
        // Saroday API wraps response: { success, data, ... }
        return { body, elapsedMs };
      } catch (err) {
        if (err.message.startsWith("Saroday API error")) throw err;
        throw new Error(`Network error calling Saroday API: ${err.message}`);
      }
    }
Behavior3/5

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

No annotations provided. The description indicates a read-only lookup returning definitions, but does not disclose whether it is idempotent, any authentication requirements, or rate limits. With no annotations, the description carries the full burden but only states what it does, not behavioral traits.

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?

Single-sentence description is front-loaded with the core action, then lists categories. It is informative but somewhat long; could be split for readability. No wasted words.

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 simple input (1 param, no output schema), the description adequately covers the tool's purpose and scope. It does not mention if the term is case-sensitive or if partial matches are allowed, but the example terms compensate. Reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% (parameter 'term' described in both schema and description). The description adds value by listing example terms and categories, providing context beyond the schema's generic description.

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 states it looks up glossary terms for Myeongrihak, listing specific categories (십성, 신살, 합충형파해, 12운성) and over 80 terms. The verb '조회' and resource '명리학 용어 풀이' are specific, distinguishing it from sibling tools.

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?

No explicit guidance on when to use versus alternatives. The context signals show sibling tools like calculate_saju, but the description does not compare them or provide exclusions. Usage is implied: lookup a term when you need its definition.

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/yolstudio26-oss/saroday-mcp-server'

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