Skip to main content
Glama
cwon-z

icampus-mcp

by cwon-z
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_lectures

Read-only

List lecture videos and materials with completion status and deadlines, filterable by course, week, or kind, and optionally include attendance summaries to track coursework.

Instructions

Lecture videos/materials with completion and attendance as iCampus shows them, soonest deadline first. By default: items already open, not completed, whose deadline (incl. late period) has not passed.

Args:
    course: course ID, code or part of the name.
    week: week number (1 = 1주차).
    kind: e.g. video or material.
    incomplete_only: only items reported as not completed (unknown completion is left out).
    include_upcoming: also items that have not opened yet.
    include_overdue: also items whose deadline has passed (missed, possibly still viewable).
    include_attendance: add each course's official per-lesson attendance summary.
    limit: maximum items returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNo
weekNo
limitNo
courseNo
include_overdueNo
incomplete_onlyNo
include_upcomingNo
include_attendanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The description adds substantial behavior beyond the read-only/hints: soonest-deadline-first sorting, default filtering, unknown-completion exclusion, overdue items 'possibly still viewable', and per-lesson attendance summaries. This goes beyond what annotations alone convey.

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?

The description is front-loaded with the core purpose and default behavior, followed by a compact, well-formatted Args list. Every line adds useful information with no filler or repetition of the tool name.

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?

The description covers defaults, ordering, parameter meanings, and edge-case behavior well. It does not describe the raw response shape, but no output schema exists; still, the information provided is sufficient for an agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description documents all 8 parameters with valuable semantics: course accepts ID/code/partial name, week is 1-based, kind is exemplified, incomplete_only excludes unknown completion, and include_overdue explains missed items may still be viewable. It fully compensates for the schema's lack of descriptions.

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?

The description uses a specific verb and resource ('Lecture videos/materials') and adds meaningful scope: completion, attendance, and iCampus presentation. It is clearly distinguishable from sibling tools like list_announcements, list_courses, and list_tasks by focusing on lectures with deadline ordering.

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 default filter is explicitly stated: items already open, not completed, and with a deadline that has not passed. This gives clear context for when the tool is appropriate, though it does not explicitly name alternatives or say when to avoid using it.

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

Deploy Server

Other Tools