Skip to main content
Glama

알잘 입시

대학 입시 정보 찾기

search_admissions
Read-onlyIdempotent

Search Korean university admissions data by university, major, admission track, or recruiting-unit name. Returns up to 5 matches, each with a one-line summary, an id for get_admission_details, and the ipsi.aljal.kr page URL. Source: the official admission guide of each university. Matching is by Korean name, not by meaning: English names are not matched, so pass short Korean names such as 의예과, 간호, 지역균형, 학생부종합, 축구. Results are in Korean. 대학명·학과명·전형명·모집단위명으로 찾습니다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_admissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoOptional entrance year (학년도), e.g. 2027.
queryYesMajor, track, or unit name in Korean (translate English first), e.g. "의예과", "지역균형", "간호". A university name alone also works, e.g. "서울대". 학과명·전형명·대학명.
schoolNoOptional university name or common short name in Korean to narrow results, e.g. "서울대", "숙명여대", "이대". 대학명 또는 약칭.
seasonNoOptional admission round: 수시 (early) or 정시 (regular).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description discloses the hard result cap of 5, the per-result contents (one-line summary, id, page URL), the data source (official university admission guides), and that results are in Korean. It also warns that matching is lexical rather than semantic, which is exactly the kind of non-obvious behavior an agent needs before calling.

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 definition is front-loaded with purpose and result shape, then matching constraints, which is a sensible order. The final Korean sentence (대학명·학과명·전형명·모집단위명으로 찾습니다) largely restates the first sentence's field list, a minor redundancy.

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?

With four parameters, no output schema, and rich annotations, the description covers what an agent needs: what is searched, the 5-result limit, the exact return fields, the id handoff to get_admission_details, and the Korean-name matching constraint. The remaining parameter details are fully documented in the schema.

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 coverage is 100%, so the baseline would be 3, but the description adds real semantic guidance: the query must be a short Korean name, English is not matched, and example tokens are given. It does not explain how year or season interact with the query, leaving those to 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?

The description opens with a specific verb and resource: search Korean university admissions data by university, major, admission track, or recruiting-unit name. It also states the result shape (up to 5 matches with summary, id, and URL) and names get_admission_details as the follow-up tool. It does not explicitly distinguish itself from browse_admissions, so sibling differentiation is incomplete.

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?

Strong guidance on how to formulate the query: matching is by Korean name, not meaning, English names are not matched, and short Korean names like 의예과 or 지역균형 should be passed. It also routes the agent to get_admission_details using the returned id. However, it never states when to prefer this over browse_admissions or when to use year/season filtering versus a text query.

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