itu-mcp

Overview Schema Source Related Servers Discussions Admin

Get Course Assignments

get_course_assignments

Read-onlyIdempotent

Return a course's assignment list and, by default, each assignment detail/upload page. Set include_details=false for a list-only read.

Instructions

Return a course's assignment list. By default also fetches each assignment detail/upload page; set include_details=false for a faster list-only read.

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_assignments"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`course`	Yes
`compact`	No
`include_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_assignmentsDictOutput"New value: +"get_course_assignmentsOutput"

First observedv0.2.0Jul 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare the safe read profile (readOnly, idempotent, non-destructive), so the bar is lower. The description still adds meaningful behavior beyond that: by default the call fans out to fetch each assignment's detail/upload page, and this can be disabled for speed. That cost/behavior disclosure is exactly the kind of context annotations don't carry.

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 sentences, zero waste. The default behavior is stated first and the opt-out is front-loaded immediately after, so the agent can act without scanning.

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 not be described, and the read-only annotations cover safety. The description completes the picture on default-vs-optimized behavior, but leaves the limit/compact parameters and course identifier format unaddressed.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate, and it only explains include_details (the most consequential flag) while leaving limit and especially the ambiguous compact parameter undefined. The 'course' argument is self-evident, but the overall coverage gap keeps this at a partial-compensation level.

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 a course's assignment list. This is clearly scoped to a single course, distinguishing it from siblings like get_dashboard_assignments. It does not explicitly name any sibling, so it stops short of a 5.

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?

It gives a real tradeoff for one parameter (default fetches details; include_details=false is a faster list-only read), which is genuine usage guidance. However, there is no when-to-use-this-vs-alternatives direction, e.g. versus get_dashboard_assignments or get_assignment_upload_slots, so guidance is implied rather than explicit.

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

Deploy Server