itu-mcp

Overview Schema Source Related Servers Discussions Admin

Get Course Overview

get_course_overview

Read-onlyIdempotent

Retrieve a combined overview of a course, including sections, announcements, assignments, files, grades, message board, attendance, and remote learning routes.

Instructions

Return a combined view of a course's sections, announcements, assignments, files, grades, message board, attendance, and remote learning routes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "course": "<course>"
    },
    "name": "get_course_overview"
  }
}

Input Schema

Name	Required	Description	Default
`course`	Yes
`compact`	No
`refresh`	No
`file_max_depth`	No
`include_assignment_details`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.2.1Oct 14, 2026

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_course_overviewDictOutput"New value: +"get_course_overviewOutput"

First observedv0.2.0Jul 10, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the aggregation scope but says nothing about what 'refresh' triggers (network re-fetch / cache invalidation) or the performance cost of the combined pull, which are the behaviors an agent would actually need.

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 dense sentence that front-loads the verb and enumerates scope with zero filler. Efficient, though the long comma list trades readability for compactness.

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 detail is rightly omitted, and annotations cover safety. However, with 5 parameters at 0% schema coverage and no description of them, plus an unexplained 'refresh' mutation-ish behavior, the definition leaves real gaps for correct invocation.

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 5 parameters, so the description carries the full burden and fails it: compact, refresh, file_max_depth, and include_assignment_details are never mentioned. Only faint hints exist via the nouns 'files' and 'assignments' in the return list, which does not convey what those flags change.

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?

Clear verb ('Return') and resource ('a course's sections, announcements, assignments...'), and it explicitly identifies itself as a 'combined view', which distinguishes it from the ~10 granular get_course_* siblings. It stops short of naming those siblings or stating the aggregate-vs-granular tradeoff, so an agent must infer the differentiation.

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?

The word 'combined' implies this is the bulk-fetch option versus get_course_sections/get_course_announcements/etc., but there is no explicit when-to-use statement, no condition for choosing it over the granular siblings, and no note on cost or latency of fetching everything.

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

Deploy Server