Skip to main content
Glama
yatuk

itu-mcp

by yatuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Public Course Prerequisites

get_public_course_prerequisites
Read-onlyIdempotent

Read prerequisite details from a course's public OBS DersBilgi page without login; returns structured codes, names, groups, and types.

Instructions

Read prerequisite details from a course's public OBS DersBilgi page. No login required. Returns structured prerequisite list with codes, names, groups, and types.

Input Schema

NameRequiredDescriptionDefault
ders_noYes
brans_koduYes

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

TDQS

A3.6/5.0
Behavior4/5

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

Annotations cover safety (readOnly, idempotent, non-destructive). The description adds context beyond annotations: it discloses the data source (OBS DersBilgi public page), that no authentication is required, and describes the return shape (codes, names, groups, types). This is real added value.

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?

Three short, front-loaded sentences. Every sentence earns its place: purpose, auth constraint, return shape. No filler.

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?

For a read-only helper with a rich output schema and full annotation coverage, the description covers source, auth, and return structure adequately. The main gap is parameter meaning, which the description could helpfully disambiguate given the 0% schema coverage.

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% — neither the description nor schema explains what 'ders_no' or 'brans_kodu' mean or their formats. The description could have clarified that these are course number and subject/branch code, but it doesn't, leaving both parameters opaque.

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 (read), resource (prerequisite details), and source (public OBS DersBilgi page). Clear and distinct from sibling obs_get_course_prerequisites, which likely requires login — the word 'public' is the differentiator, though the description doesn't explicitly call out that distinction.

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?

Implies usage via 'No login required,' suggesting it's for unauthenticated contexts. However, it never explicitly says when to use this vs obs_get_course_prerequisites or what inputs must be sourced from where. Usage context is inferable but not stated.

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