Skip to main content
Glama

find_academic_calendar_events

Read-onlyIdempotent

숭실대학교 학사일정을 연도, 월, 키워드로 필터링해 반환합니다. 수강신청·개강·종강·시험 같은 일정 검색에 사용합니다.

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": "find_academic_calendar_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo조회할 연도(예: 2026). 생략 시 현재 연도.
limitNo반환할 최대 일정 수. 기본 20, 최대 50.
monthNo조회할 월(1-12). 생략 시 전체 월.
keywordNo일정명 또는 카테고리 키워드. 예: 수강신청, 기말고사.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the filtering/scoping behavior but does not mention result ordering, pagination, empty-result behavior, or what fields the returned events contain.

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?

Two tight sentences: the first states what the tool returns and how filtering works, and the second gives practical usage examples. There is no repetition, filler, or irrelevant detail.

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 read-only, filtered-list tool, the description covers the key facts: resource, filters, and common use cases, and the schema documents all parameters. The main gap is the lack of explicit differentiation from get_academic_calendar and the absence of any mention of the returned event structure, though neither is strictly required for invoking the tool correctly.

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?

All parameters are fully documented in the schema, so the baseline is 3. The description mostly restates 'year, month, keyword' filtering and provides examples already present in the keyword parameter description, adding no new semantic information 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?

The description clearly states the action ('returns Soongsil University academic calendar events') and the filters ('year, month, keyword'), and it gives concrete use cases like course registration and exams. However, it does not explicitly distinguish this tool from the sibling get_academic_calendar, which appears to target the same resource.

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 provides clear usage context: use it to search academic calendar events filtered by year, month, and keyword, especially for events like registration, class start/end, and exams. It does not, however, name alternatives or state when not to use it, leaving the comparison with sibling tools implicit.

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