Skip to main content
Glama

Get catalog course description

get_course_description
Read-only

Fetches a CMU course's catalog description, units, semesters offered, prerequisites with minimum grades, corequisites and website. Use it to verify requirements before enrolling.

Instructions

The current CMU Undergraduate Catalog entry for a course: title, semesters usually offered, units, description, prerequisites (with minimum grades, e.g. '15-112 Min. grade C'), corequisites and course website. Term-independent. Only the current catalog year is available, and graduate courses are often absent; get_course_info covers any offered course.

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_number": "<course_number>"
    },
    "name": "get_course_description"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds real value on top: it discloses catalog-year staleness and the systematic gap for graduate courses, which are exactly the failure modes an agent needs to anticipate. It stops short of saying whether a miss returns an error or an empty result, which would have made it a 5.

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?

Three sentences, front-loaded with the resource and its field list, then the scope caveats, then the alternative. Nothing is redundant with the title, and the example prerequisite string ('15-112 Min. grade C') earns its place by showing output shape.

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?

For a one-parameter read-only lookup with no output schema, the description fully compensates by enumerating returned fields and stating the coverage limits of the data source. An agent has everything needed to call it and to interpret a missing graduate course.

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?

There is a single required parameter and schema description coverage is 100%, with the schema itself supplying accepted formats ('15-122', '15122', '21-127'). The description adds no further meaning about course_number, so the baseline 3 applies – the schema does all the work here.

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?

The description states a specific resource (the current CMU Undergraduate Catalog entry for a course) and enumerates exactly what comes back: title, semesters offered, units, description, prerequisites with minimum grades, corequisites, and website. It also distinguishes itself from the sibling get_course_info by noting it is term-independent and catalog-only, so an agent can choose between them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives explicit when-not-to-use conditions (only the current catalog year is available; graduate courses are often absent) and names the alternative, get_course_info, along with its coverage ('any offered course'). The mapping from situation to tool is clear enough that an agent knows to fall back to the sibling for term-specific or graduate offerings.

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