Skip to main content
Glama

get_undergraduate_exam_schedule

Read-onlyIdempotent

Retrieve General Access exam dates and times for an undergraduate course by course code in the latest or specified published term.

Instructions

Get public General Access exam dates and times for a course in the latest or specified published term.

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": {
      "course_code": "<course_code>"
    },
    "name": "get_undergraduate_exam_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
semesterNo
course_codeYes
academic_yearNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and open-world behavior, and the description adds real context on top: results are limited to 'public General Access' exams (excluding restricted/non-public exam types) and the term defaults to the latest published one when not supplied. It stops short of stating what happens when no published schedule exists.

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?

A single tight sentence with the resource and the default-term behavior front-loaded and no filler. Every clause carries information the agent needs.

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

Completeness3/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 not be described, and the safety profile is handled by annotations. The remaining gap is the undocumented parameter formats (0% schema coverage) and the absence of any routing hint toward the graduate or index-schedule siblings.

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 0%, so the description must compensate. It clarifies that course_code identifies the course and that semester/academic_year are optional, defaulting to the latest published term, but it gives no format for academic_year (e.g. 2024 vs 24) or semester values beyond the schema enum.

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?

Specific verb ('Get') plus a precise resource: public General Access exam dates and times for a course. The word 'undergraduate' in the name plus 'General Access' scoping separates it from get_graduate_course_schedule, though the description never names that sibling explicitly.

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 by 'for a course' and by the 'latest or specified published term' phrasing, which tells the agent the term arguments are optional. There is no explicit when-to-use vs when-not guidance and no pointer to get_graduate_course_schedule for graduate courses.

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