Skip to main content
Glama
yatuk

itu-mcp

by yatuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

OBS Graduation Remaining

obs_get_graduation_remaining
Read-onlyIdempotent

Check remaining graduation requirements, academic status, and debts for an İTÜ program. Reads OBS data to map satisfied electives, list open slots and required courses, and tally credits.

Instructions

Read 'mezuniyetime ne kaldı', academic status, and debts for a program. The 'summary' field maps each filled elective slot to the real course that satisfies it (e.g. BLG 422E → '7th Sems. Elect. Course I (MT)'), lists open slots and remaining required courses, and tallies credits. Read 'summary' first; the raw 'graduation' payload is the unreduced source.

Input Schema

NameRequiredDescriptionDefault
program_idNo

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: -"obs_get_graduation_remainingDictOutput"New value: +"obs_get_graduation_remainingOutput"
  2. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare the full safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower. The description adds one behavioral detail beyond annotations: the 'summary' field is a reduced/derived view while 'graduation' is unreduced, which tells the agent how to interpret what a read returns. It says nothing about auth requirements, session validity, or latency for this OBS-backed call.

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?

Three sentences, each carrying load: purpose, then the summary-field semantics, then the read-order instruction. The summary sentence is dense and slightly nested, but the key directive ('Read summary first') sits at the front of its clause rather than being buried.

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 enumerated, yet the description goes further by explaining the semantic transformation the summary field performs (slot-to-course mapping, open slots, credit tally) — context an output schema cannot convey. The only real gap is missing auth/session context for an OBS-scoped read.

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 coverage is 0% for the single optional program_id parameter, so the description must compensate and mostly does only indirectly — 'for a program' frames the parameter's role but gives no format, no default behavior when null, and no indication of which program is assumed otherwise. It does not add syntax or resolution detail beyond the schema's title 'Program Id'.

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: reads graduation-remaining status, academic standing, and debts for a program, echoing the Turkish student phrase 'mezuniyetime ne kaldı'. Clear to an agent, though it never distinguishes itself from the nearby plan_remaining_courses sibling, which an agent could easily pick by mistake.

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 only implied by the resource name; there is no explicit when-to-use, no prerequisites (e.g. needing an authenticated OBS session), and no routing statement versus plan_remaining_courses or archive_* tools. The one concrete directive — read 'summary' first, treat 'graduation' as the raw source — is genuinely useful guidance but is about output consumption, not about when to select this tool.

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