Skip to main content
Glama

입시 목록 보기

browse_admissions
Read-onlyIdempotent

List what the data covers, grouped, in Korean: coverage (how many universities and which entrance years), the universities (optionally by region), the academic fields (계열), the major groups (과그룹, e.g. 간호·보건, 컴퓨터·소프트웨어), or the majors in one field or group with university counts and seats. Use it to see which universities and majors are available, or to find the Korean names that search_admissions matches. Major lists show up to 30 entries, largest seats first, each with an id for get_admission_details and the page URL. 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": {
      "list": "<list>"
    },
    "name": "browse_admissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
listYesWhat to list: coverage (current scope), schools (universities), fields (계열), groups (과그룹), or majors (학과, narrow with field or group).
fieldNoOptional academic field name in Korean to narrow groups or majors, e.g. "의약·보건", "공학", "인문". 계열.
groupNoOptional major group name in Korean to narrow majors, e.g. "간호", "컴퓨터", "경영·회계". 과그룹.
regionNoOptional region in Korean to narrow schools, e.g. "서울", "경기", "부산". 지역.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive/open-world. The description adds behavior beyond them: Korean-only results, truncation at 30 entries with largest-seats-first ordering, and that each major carries an id plus a page URL. It doesn't say how to retrieve entries beyond the 30-entry cap, which is the one remaining gap.

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 enumeration of list modes followed by purpose and output shape; every sentence carries information. Minor redundancy in stating Korean output twice plus a Korean restatement of the same list at the end.

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?

No output schema exists, and the description compensates by describing return content (university counts, seats, ids, URLs) and result language. Only the truncation/pagination behavior beyond 30 entries is left unexplained.

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 baseline is 3. The description adds relational meaning the schema only implies: field narrows groups or majors, group narrows majors, region narrows schools, with concrete group examples like 간호·보건 and 컴퓨터·소프트웨어.

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?

States a specific verb (list) and enumerates exactly what can be listed: coverage, schools, fields, groups, majors. It is clearly distinguished from search_admissions (name lookup) and get_admission_details (per-major id lookup), so an agent can select it from siblings without opening the schema.

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 explicit use cases: 'see which universities and majors are available, or to find the Korean names that search_admissions matches.' That routes the agent to and away from search_admissions. It stops short of explicit exclusions (e.g., don't use this for schedules or detail records), so not a 5.

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