Skip to main content
Glama

Get course prerequisites, notes and reservations

get_course_info
Read-only

Retrieve a CMU course's Schedule of Classes details for a semester, including description, prerequisites and corequisites, cross-listings, special permission needs, notes, and section seat reservations.

Instructions

The Schedule of Classes detail page for one course in a semester: description, prerequisite and corequisite expressions as the SOC states them (e.g. '15112 or 02120') plus the course numbers they mention, cross-listed courses, whether special permission is required, notes, per-section reservations (seats held for certain students), and related URLs.

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": {
      "semester": "<semester>",
      "course_number": "<course_number>"
    },
    "name": "get_course_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
semesterYesSemester code such as "S27" (Spring 2027), "F26" (Fall 2026), "M26" (Summer 2026). Names like 'Spring 2027' also work. Use list_semesters to see what is published.
course_numberYesCMU course number, e.g. "15-122", "15122" or "21-127".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful context about what the SOC actually returns, including the raw prerequisite string format ('15112 or 02120'), but says nothing about behavior when a course is absent from a semester or how stale/complete the underlying data is.

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?

A single front-loaded sentence that identifies the resource first and then enumerates payload fields; the parenthetical examples ('15112 or 02120', 'seats held for certain students') clarify ambiguities rather than pad. Slightly list-heavy but nothing is wasted.

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?

With no output schema, the description carries the burden of describing returns and does so thoroughly, enumerating each field category. Only gaps are error/not-found behavior and whether special-permission or reservation data can be missing.

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 100%, and the schema already gives semester code formats, the list_semesters pointer, and flexible course-number formats. The description adds no parameter-level meaning, so the baseline of 3 applies.

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?

The description names a specific resource and scope: the Schedule of Classes detail page for one course in one semester, and enumerates the concrete payload (prerequisites, corequisites, cross-listings, special permission, notes, per-section reservations, URLs). An agent knows exactly what data comes back, but there is no explicit differentiation from close siblings like get_course_details or get_course_description.

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 through content enumeration — an agent needing prerequisite expressions or seat reservations can infer this is the tool — but there is no explicit when-to-use statement and no routing against the near-identical siblings get_course_details and get_course_description.

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