Skip to main content
Glama
yolstudio26-oss

Saroday MCP Server

discover_saroday_api

Retrieve Saroday API metadata including endpoints, documentation links, and usage limits. Use this tool first to understand available tools for Korean Saju calculation and fortune-telling glossary lookup.

Instructions

Saroday API 메타 정보 조회. 사용 가능한 엔드포인트, 문서 링크, 호출 한도 등을 반환합니다. 처음 사용할 때 한 번 호출해서 어떤 도구가 있는지 파악할 수 있습니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that calls Saroday API /api/v1 to fetch API metadata (endpoints, docs, rate limits) and returns a formatted markdown text response.
    async function handleDiscoverApi() {
      const { body } = await callSarodayAPI("/api/v1");
      const d = body.data;
    
      let text = `# ${d.name} ${d.version}\n\n`;
      text += `${d.description}\n\n`;
      text += `**문서:** ${d.docs}\n`;
      text += `**OpenAPI:** ${d.openapi}\n\n`;
      text += `## 사용 가능한 엔드포인트\n`;
      for (const [route, desc] of Object.entries(d.endpoints || {})) {
        text += `- \`${route}\` — ${desc}\n`;
      }
      text += `\n**호출 한도:** ${d.rateLimit?.requests || 100} requests / ${d.rateLimit?.window || "1h"}\n`;
      if (d.rateLimit?.note) text += `*${d.rateLimit.note}*\n`;
    
      return { content: [{ type: "text", text }] };
    }
  • Tool definition with input schema. This tool takes no parameters (empty properties object).
    {
      name: "discover_saroday_api",
      description:
        "Saroday API 메타 정보 조회. 사용 가능한 엔드포인트, 문서 링크, 호출 한도 등을 반환합니다. " +
        "처음 사용할 때 한 번 호출해서 어떤 도구가 있는지 파악할 수 있습니다.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • index.js:365-367 (registration)
    Tool is registered via ListToolsRequestSchema handler returning the TOOLS array which includes discover_saroday_api.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
  • index.js:380-381 (registration)
    The CallToolRequestSchema switch-case dispatches "discover_saroday_api" to the handleDiscoverApi() handler.
    case "discover_saroday_api":
      return await handleDiscoverApi();
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the tool returns metadata and implies it is read-only and safe. However, it does not explicitly confirm no destructive effects, auth requirements, or rate limits for this tool itself. This is adequate but could be more explicit.

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?

The description is two sentences: the first clearly defines the tool's purpose, and the second provides usage guidance. It is front-loaded, concise, and contains no extraneous information.

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

Completeness5/5

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

For a parameterless tool with no output schema and a simple metadata purpose, the description fully covers what the tool does, what it returns, and when to use it. Sibling tools are distinct, so the agent can correctly infer its role.

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?

The input schema has no parameters, and schema description coverage is 100%. The description implicitly indicates that no parameters are needed ('call once'). It does not need to add param details, though it could explicitly state 'no parameters required.'

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 that the tool retrieves metadata (endpoints, docs, rate limits) about the Saroday API. It distinguishes itself from sibling tools like calculate_saju, get_daily_fortune, and lookup_glossary, which are specific application tools.

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?

The description explicitly advises calling this tool once at first use to understand available tools. This provides clear when-to-use guidance, though it does not mention when not to use it or specify alternatives.

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