Skip to main content
Glama

List CMU departments

list_departments
Read-only

Retrieve every Carnegie Mellon department with its code and course-number prefix to identify subject codes when searching the Schedule of Classes or filtering courses.

Instructions

Every department in the Schedule of Classes with its code (CS, MSC, ECE, ...) and the two-digit course-number prefix it owns (CS = 15, MSC = 21).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_departments"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one real behavioral fact — the word 'Every' signals an exhaustive, unfiltered, non-paginated result — but says nothing about ordering, response shape, or whether the list is stable across semesters.

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 sentence with no filler, front-loading the scope ('Every department in the Schedule of Classes') before the concrete example values. Nothing could be removed without losing information.

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 and no parameters, the description carries the burden of explaining the return values, and it does so with both field names and examples. It leaves minor gaps — result ordering and the exact format of the code string — but is adequate for a trivial enumeration call.

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 are zero parameters, which normally sets a baseline of 4, but the description's content is almost entirely about the returned fields rather than any input semantics. Since the schema is empty and fully covered, the description has little parameter meaning to add, so a 3 reflects its limited relevance to this dimension.

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 the exact resource (every department in the Schedule of Classes) and the two fields returned (department code and its two-digit course-number prefix, with CS/MSC/ECE examples), so an agent can tell this is a department directory, not a course or building lookup. It stops short of explicitly contrasting with siblings like list_buildings or search_courses, and is a noun-phrase fragment rather than a verb+resource statement.

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: the mention of department codes and course-number prefixes suggests this is the lookup step before searching or decoding course numbers, but the description never states when to call it or when another sibling is better. With zero parameters and no alternatives named, an agent must infer the routing itself.

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