Skip to main content
Glama
Sign In
itu-mcp

itu-mcp

by yatuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

OBS Course Prerequisites

obs_get_course_prerequisites
Read-onlyIdempotent

Query a course's prerequisite and postrequisite relationships from the OBS public catalog, with optional chain depth up to 10 levels.

Instructions

Public, no login required. Query prerequisite and postrequisite relationships for a course from the OBS public catalog. Supports chain queries up to 10 levels deep.

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_code": "<course_code>"
    },
    "name": "obs_get_course_prerequisites"
  }
}

Input Schema

NameRequiredDescriptionDefault
directionNoprerequisites
max_depthNo
course_codeYes

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_course_prerequisitesDictOutput"New value: +"obs_get_course_prerequisitesOutput"
  2. Addedv0.2.3

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds useful non-redundant context: no authentication needed and a hard 10-level cap on chain queries. That depth limit is a genuine behavioral constraint the agent would otherwise not know.

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 tight sentences, zero filler, with the public-access note and query scope front-loaded ahead of the depth caveat.

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 the access/depth notes are helpful. However, with 0% schema coverage across three parameters and no explanation of direction values or course_code format, the definition leaves gaps for correct invocation.

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 carry parameter meaning. It partially compensates by implying the direction values (prerequisite vs postrequisite) and the depth bound ('up to 10 levels deep'), but never names or explains the direction/max_depth parameters or the course_code format.

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 (query) and resource (prerequisite/postrequisite relationships) scoped to the OBS public catalog. An agent can tell what it does, though it does not explicitly differentiate itself from the very similar sibling get_public_course_prerequisites.

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?

Provides context ('Public, no login required', chain queries up to 10 levels deep) that implies when this tool applies, but gives no explicit when-to-use/when-not guidance and never mentions the near-duplicate sibling get_public_course_prerequisites or other eligibility tools.

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