Skip to main content
Glama

알잘 입시

입시 일정 보기

get_admission_schedule
Read-onlyIdempotent

List admission schedule dates as written in the official guides. With a university name: that university's application, document, exam, and announcement dates. Without one: the nationwide common calendar (CSAT date, score release, application windows). Returns up to 30 dated lines in Korean, the source, the page URL, and a calendar file (.ics) URL. 학교별 입시 일정 또는 모든 수험생 공통 일정입니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_admission_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional end date YYYY-MM-DD. Defaults to 90 days after the start.
fromNoOptional start date YYYY-MM-DD. Defaults to today (Korea time).
schoolNoOptional university name or short name in Korean, e.g. "서울대", "연세대". Omit for the nationwide common calendar. 비우면 공통 일정.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world behavior, so the description's contribution is the output disclosure: up to 30 dated lines in Korean plus source, page URL, and .ics URL, which is meaningful since no output schema exists. It stops short of saying how current the guide data is or what happens when a school returns nothing.

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?

Front-loaded with the verb and scope, and the mode split comes early. The closing Korean sentence restates the school/nationwide distinction already given in English, which is redundant, though it serves bilingual readers.

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?

For a three-optional-parameter read tool with no output schema, the description covers scope selection, return shape, size cap, language, and auxiliary artifacts (source, URL, .ics). Only edge cases like empty results or data recency are unaddressed.

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 coverage is 100%, so all three parameters are already documented with formats and defaults. The description only reinforces the school parameter's omit-behavior and the date-range framing, adding little syntax or semantics 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?

States a specific verb and resource ("List admission schedule dates") and defines two distinct scopes: a named university's application/document/exam/announcement dates versus the nationwide common calendar. It does not differentiate itself from siblings such as get_admission_details or search_admissions, which keeps it from a 5.

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?

Gives clear contextual guidance for the two modes — supply a school name for that university's dates, omit it for the CSAT/score-release/application-window calendar. No exclusions or sibling alternatives are named, so the agent has to infer when search_admissions or get_admission_details would be better.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources