itu-mcp

Overview Schema Source Related Servers Discussions Admin

Get Course Attendance

get_course_attendance

Read-onlyIdempotent

Read a course's Ninova Yoklama page to retrieve instructor-recorded LMS attendance, not official OBS attendance. For official OBS records with absence-risk summaries, use obs_get_attendance.

Instructions

Read the Ninova 'Yoklama' page for a course — attendance as the instructor recorded it in the LMS, not the official OBS record. For official attendance with an absence-risk summary, use obs_get_attendance instead.

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

Input Schema

Name	Required	Description	Default
`course`	Yes

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_attendanceDictOutput"New value: +"get_course_attendanceOutput"

First observedv0.2.0Jul 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the data is instructor-recorded LMS data, not the official OBS record, which affects trust and interpretation. It does not discuss auth requirements, but that gap is minor.

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 front-loaded sentences with zero filler: the what/where comes first, the alternative routing second. Every clause earns its place.

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

Completeness5/5

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

For a simple read-only lookup with an output schema present, return values need not be explained and annotations cover safety. The description supplies the one thing that matters – the distinction from the official OBS attendance tool – so nothing essential is missing.

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% for the single 'course' parameter, so the description carries the burden. Its phrase 'for a course' implies a course identifier but gives no format (course code, ID, section), so it only partially compensates. A 3 reflects the modest value added over the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Read) and resource (the Ninova 'Yoklama' page for a course) and immediately scopes it against the OBS record. An agent can distinguish it from obs_get_attendance without opening either schema.

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

Usage Guidelines5/5

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

Explicitly names the alternative (obs_get_attendance) and the condition that selects it ('official attendance with an absence-risk summary'). The when-to-use routing is unambiguous.

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

Deploy Server