Skip to main content
Glama
Sign In
itu-mcp

itu-mcp

by yatuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

OBS Elective Group

obs_get_elective_group

Read an official elective group by group_id to view eligible courses, current undergraduate offerings, CRNs, meeting times, and section eligibility. OBS login is required for eligibility checks.

Instructions

Read any official elective group by group_id, including eligible course membership, current undergraduate offerings, CRNs, meeting times and student-specific section eligibility. Each section is checked independently, up to 8 sections per call. Membership and schedules are public; eligibility requires an OBS session. Unknown source data stays unknown. Does not change the saved draft or registration.

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": {
      "group_id": "<group_id>"
    },
    "name": "obs_get_elective_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.1

TDQS

A3.9/5.0
Behavior4/5

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

Adds real context beyond annotations: eligibility requires an OBS session while membership/schedules are public, sections are checked independently capped at 8 per call, and unknown source data is preserved. The caveat about not changing the draft/registration is consistent with readOnlyHint=false rather than contradicting it, so no flag.

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?

Front-loaded with the verb and resource, and the following sentences each add a distinct constraint (auth, batch cap, unknown handling, side effects). Slightly dense but 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?

An output schema exists so return values need no prose, and the description still covers scope, auth, and batching. The only gap is group_id semantics, which is minor for a single integer id.

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?

Only one parameter (group_id) with 0% schema description coverage, and the description merely restates the name ("by group_id") without format, source, or lookup guidance. Low coverage would warrant compensating detail that is absent, so this stays at baseline.

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?

Specific verb+resource ("Read any official elective group by group_id") plus an explicit inventory of what it returns: membership, undergraduate offerings, CRNs, meeting times, and section eligibility. This is distinguishable from siblings like obs_get_registration_draft or obs_search_courses.

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 implied (look up an elective group by id) but no alternatives are named and no when-not conditions are given. The closing caveat ("Does not change the saved draft or registration") faintly separates it from draft-mutating tools but does not route the agent to a specific sibling.

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