Skip to main content
Glama
yatuk

itu-mcp

by yatuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Sync All Courses

sync_all_courses

Fetch all visible İTÜ Ninova LMS courses, save a tracking snapshot, and return newly detected changes since the last sync. Assignment details are skipped by default for speed.

Instructions

Fetch all visible courses, store a tracking snapshot, and return newly detected changes since the previous sync. Assignment detail pages are skipped by default for speed.

Input Schema

NameRequiredDescriptionDefault
course_limitNo
include_filesNo
file_max_depthNo
include_assignment_detailsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.2.1
    • 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: -"sync_all_coursesDictOutput"New value: +"sync_all_coursesOutput"
  2. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

With readOnlyHint=false and openWorldHint=true, the description usefully discloses the side effect (stores a tracking snapshot) and the default content-skipping behavior, which matches the non-idempotent, non-destructive annotations. It adds real context beyond the structured fields, though it doesn't cover rate/cost or re-sync implications.

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, front-loaded with the core action and scope, followed by the key default behavior. No filler or redundancy.

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?

An output schema exists, so return values need no explanation, and the description covers the mutation/snapshot semantics and one important default. The remaining gap is that four schema parameters with zero coverage are largely unexplained.

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% across 4 parameters, so the description must compensate. It implies the default of include_assignment_details (false) via 'skipped by default', but says nothing about course_limit, include_files, or file_max_depth/default depth of 3, leaving three parameters undocumented in both places.

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 compound verb set (fetch, store snapshot, return changes) and the resource (all visible courses), plus a behavioral fact (assignment pages skipped by default). It distinguishes itself from plain listing tools like list_courses by emphasizing persistent tracking and diffing, though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: this is the tool to run for change detection since the previous sync. The 'skipped by default for speed' note hints at a tradeoff but there is no explicit when-to-use, when-not-to-use, or alternative (e.g. snapshot_page/diff_snapshot) guidance.

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