Skip to main content
Glama

Get course sections and meeting times

get_course_details
Read-only

Fetch a course's sections, meeting times, minis, and campus for a semester to check schedule conflicts and plan enrollment.

Instructions

Every section of one course in a semester: lectures with their nested recitations/labs, mini (1-6; minis 1/3/5 are the first half of the semester, 2/4/6 the second), and each meeting's days, begin/end time, campus and delivery mode. Extra meetings (e.g. an evening exam slot) appear as additional meetings of the same section. Seats, waitlists, rooms and instructors are not published publicly.

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_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
campusNoOnly sections taught on this campus: "Pittsburgh", "Doha", "Silicon Valley", ... Default "any". CMU lists other campuses' sections inside the same course.any
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.7/5.0
Behavior4/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 and the description is freed to add semantics. It does so well: it explains the mini numbering convention (1-6, odd = first half, even = second half), clarifies that extra meetings such as an evening exam appear as additional meetings of the same section rather than a separate entity, and discloses what data is deliberately absent. It does not discuss result size, empty results, or ordering, which are the remaining behavioral gaps.

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?

Two sentences, densely packed but front-loaded with the core scope before the mini convention and the negative disclosure. Every clause carries real information; the run-on enumeration of output fields is the only minor cost to readability.

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 return-value burden and does it thoroughly — nesting of lectures and recitations/labs, mini conventions, per-meeting fields, and out-of-scope fields are all covered. What is missing is the shape of the response itself (how sections are identified or ordered) and what happens when a course has no published sections, which matters for a tool an agent may call blind.

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%, so all three parameters (semester, course_number, campus) are already documented, including the semester code format and the campus default of 'any'. The description adds no parameter-level meaning beyond what the schema provides; in fact the campus filter is never mentioned in prose, only campus as an output field. Baseline 3 is appropriate when the schema carries the parameter burden.

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 opens with a precise scope statement — 'Every section of one course in a semester' — and enumerates the exact payload (lectures, nested recitations/labs, meeting days/times, campus, delivery mode). It is a noun phrase rather than a verb, and it never names a sibling to contrast with (e.g. get_course_description or search_courses), so the differentiation is inferred rather than stated.

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: an agent can infer this is the tool for retrieving sections/meeting times once a course number and semester are known. There is no explicit when-to-use vs when-not, no mention of search_courses as the discovery path, and no statement that semester must come from list_semesters (that hint lives in the schema, not the description). The only steering is the closing note that seats, waitlists, rooms and instructors are not published, which usefully tells the agent not to call this for those fields.

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