Skip to main content
Glama
yatuk

itu-mcp

by yatuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Academic Calendar

get_academic_calendar
Read-onlyIdempotent

Fetch İTÜ academic calendar for semester dates, exams, holidays, and registration periods. No login needed.

Instructions

Read the İTÜ academic calendar — semester dates, exams, holidays, registration periods (public, no login).

Input Schema

NameRequiredDescriptionDefault
queryNo
date_toNo
categoryNo
date_fromNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.2.1
    • addedInput schema / properties / category
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Category"
+}
    • addedInput schema / properties / date_from
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Date From"
+}
    • addedInput schema / properties / date_to
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Date To"
+}
    • addedInput schema / properties / query
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Query"
+}
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / properties
      Added value: +{
+  "result": {
+    "additionalProperties": true,
+    "title": "Result",
+    "type": "object"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "result"
+]
    • changedOutput schema / title
      Previous value: -"get_academic_calendarDictOutput"New value: +"get_academic_calendarOutput"
  2. Addedv0.2.3

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds the '(public, no login)' auth context, which is genuinely beyond the annotations. It does not describe pagination, filtering behavior, or result shape.

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?

A single front-loaded sentence with the resource named first and the content enumeration following. No waste, though it is terse enough to omit useful detail rather than being optimally informative.

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-value format need not be explained, and the description covers the topical content well. The main gap is the four undocumented optional parameters, which are neither described in the schema nor the description.

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 coverage is 0% across four parameters (query, date_to, date_from, category) and the description mentions none of them. It does not explain what 'query' searches, what format dates take, or what 'category' accepts, leaving the agent to infer everything from parameter names.

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 ('Read') and resource ('İTÜ academic calendar') and enumerates the content covered (semester dates, exams, holidays, registration periods). It is clear what the tool returns, though it does not explicitly contrast itself with siblings like get_upcoming_deadlines or get_public_exam_schedule.

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?

The description offers no when-to-use guidance or alternatives; it never explains how this differs from get_upcoming_deadlines, get_public_exam_schedule, or get_personal_exam_calendar. The '(public, no login)' note is a mild access hint but not a usage rule.

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