POSTECH PLMS MCP

plms_export_calendar

Read-onlyIdempotent

Export upcoming course deadlines as an ICS calendar file for a chosen number of days or specific course. No calendar accounts are modified.

Instructions

Return an ICS calendar of known upcoming deadlines; no calendar account is modified.

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

Input Schema

Name	Required	Description	Default
`days`	No
`course_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so safety is covered. The description's 'no calendar account is modified' clarifies that this is an export rather than a sync to an external calendar, which is a small but genuine addition; it says nothing about the deadline window or scope.

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?

A single front-loaded sentence with zero waste; the core action and the key non-effect are stated immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and annotations carry the safety profile. Still, for a tool with two fully undocumented parameters and a close sibling, the description leaves the agent short of what it needs to call it correctly.

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

Parameters2/5

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

Schema description coverage is 0% and neither parameter is mentioned in the description. The 'days' window and the optional 'course_id' filter are entirely undocumented, so an agent cannot know the export horizon defaults to 30 days or that results can be narrowed to one course.

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?

States a specific verb and resource ('Return an ICS calendar of known upcoming deadlines') and the output format (ICS), which is meaningful. It does not, however, distinguish itself from the very similar sibling plms_upcoming_deadlines, so an agent must guess which to call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no mention of the near-identical alternative plms_upcoming_deadlines. The agent gets no criterion for choosing this tool over that sibling, nor any prerequisite information.

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