itu-mcp

Overview Schema Source Related Servers Discussions Admin

OBS Attendance

obs_get_attendance

Read-onlyIdempotent

Read official OBS class attendance and compute absence-risk summary to check if you are nearing the allowed absence limit; for Ninova LMS records, use get_course_attendance.

Instructions

Read the official attendance record for an OBS class, with a computed absence-risk summary by default. For attendance as recorded in the Ninova LMS by the instructor, use get_course_attendance instead.

Input Schema

Name	Required	Description	Default
`course`	No
`class_id`	No
`semester`	No
`include_summary`	No
`max_absence_ratio`	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: -"obs_get_attendanceDictOutput"New value: +"obs_get_attendanceOutput"

Changed2 schema fields changedv0.2.3Jul 11, 2026

addedInput schema / properties / include_summary

Added value: +{
+  "default": true,
+  "title": "Include Summary",
+  "type": "boolean"
+}

addedInput schema / properties / max_absence_ratio

Added value: +{
+  "default": 0.3,
+  "title": "Max Absence Ratio",
+  "type": "number"
+}

First observedv0.2.0Jul 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds genuine behavioral context by disclosing that a computed absence-risk summary is returned by default, though it doesn't explain what that summary contains or how max_absence_ratio influences it.

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?

Two sentences, front-loaded with the primary capability and then the disambiguation. No waste, though the second sentence could carry a bit more parameter context at no real cost.

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 values need not be described, and sibling routing is complete. However, with five undocumented parameters and an unexplained max_absence_ratio, an agent still lacks enough info to confidently construct a correct call.

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 must carry the burden. It only implicitly signals the include_summary default behavior and says nothing about max_absence_ratio's threshold role or how course/class_id/semester interact, leaving most parameters unexplained.

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 (official attendance record) plus the scope (an OBS class), and explicitly names the sibling get_course_attendance as the contrasting tool. An agent can distinguish the two 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 routes the agent: use this for the official OBS record, use get_course_attendance for instructor-recorded Ninova LMS attendance. The when-to-use alternative is named and the condition is clear.

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

Deploy Server