Skip to main content
Glama

Get final exam times

get_final_exams
Read-only

Look up published CMU final exam schedules for multiple courses at once, returning dates, times, rooms, delivery modes, and instructors. Use it to check exam times and spot scheduling conflicts.

Instructions

Final exams from the University Registrar's published schedule for several courses at once (e.g. ["15-122", "21-127 A", "15-213 Lec 1"]): date, day, time, exam room, delivery mode, status and instructors. A recitation input also returns its lecture's exam. The registrar only publishes the current semester, around week 6; for any other semester the result says published:false. A course with no row is 'none listed', not proof of no final.

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>",
      "courses": "<courses>"
    },
    "name": "get_final_exams"
  }
}

Input Schema

NameRequiredDescriptionDefault
coursesYesCourse numbers, optionally with a section: "15-122", "15-122 A", "21-127 Lec 2".
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint by disclosing the data source's limits: the registrar publishes only the current semester around week 6, the response carries published:false otherwise, and a missing row means 'none listed' rather than proof of no final. Those caveats materially change how an agent should interpret and report results.

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?

Front-loads what is returned, then adds the recitation rule and the publication caveats in compact sentences; no filler, and the most decision-relevant caveat (missing row ≠ no final) is placed last for emphasis.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 so by listing the fields returned and the published:false case. For a two-parameter read-only lookup, nothing an agent needs to invoke or interpret it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by showing concrete course-number/section formats and by explaining that a recitation value resolves to its lecture's exam. The semester semantics are left mostly to the schema, which already documents codes and examples.

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?

States a specific verb and resource ('Final exams from the University Registrar's published schedule') plus the batch scope ('several courses at once') and enumerates the returned fields, so it is clearly distinguishable from siblings like get_course_details or 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete context: batch lookup by course number with optional section, a recitation input also returns its lecture's exam, and it points the agent to list_semesters to discover valid semester codes. It does not explicitly say when to prefer get_course_details or search_courses instead, so it stops short of full when/when-not routing.

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