Skip to main content
Glama

입시 정보 요약 보기

get_admission_details
Read-onlyIdempotent

Aljal Ipsi (알잘 입시): Get a short summary for one id returned by search_admissions: a university (documents held per entrance year), one admission guide (its tracks and seats), one admission track (eligibility, CSAT minimum, schedule as written in the guide), or a major (universities offering it and seats). Returns a summary in Korean (values quoted as written in the guide), the publication date of the guide, and the page URL, not full tables. search_admissions 가 준 id 하나의 요약입니다.

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": {
      "id": "<id>"
    },
    "name": "get_admission_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAn id from search_admissions, e.g. "univ:snu", "view:snu:2027:susi", "track:snu:2027:susi:0", "major:의예".

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?

Beyond the readOnly/idempotent/non-destructive annotations, the description adds real behavioral context: the output is a summary in Korean with values quoted verbatim from the guide, includes the guide's publication date and page URL, and is explicitly 'not full tables.' It does not cover error behavior for an invalid or stale id, which is the 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?

The purpose is front-loaded with the verb and source, and the parenthetical enumerations are dense but load-bearing. The final Korean sentence restates the opening ('search_admissions 가 준 id 하나의 요약입니다') and the 'Aljal Ipsi' branding prefix adds no selection value, so it is slightly longer than needed.

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?

With one parameter and no output schema, the description correctly takes on the burden of describing what comes back: a Korean-language summary, publication date, page URL, and not full tables. It could be more specific about the summary's internal structure, but nothing an agent needs to select and invoke the tool is missing.

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% and the id property already carries four example values, so the baseline is 3. The description adds meaning on top by mapping each id namespace to what the summary will contain (documents per entrance year, tracks and seats, eligibility/CSAT minimum/schedule, or universities and seats), which the schema does not.

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 and resource ('Get a short summary for one id returned by search_admissions') and enumerates the four entity shapes the id can address: university, admission guide, admission track, major. That enumeration plus the explicit link back to search_admissions distinguishes it from that sibling, which returns ids rather than summaries.

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 prerequisite is explicit: the id must come from search_admissions, so an agent knows this is a second step after search. What's missing is any exclusion — it never tells the agent when to prefer get_admission_schedule or browse_admissions instead, and the phrase 'schedule as written in the guide' mildly overlaps with a dedicated schedule tool.

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