Skip to main content
Glama
Sign In
GatorPath

GatorPath

by ashleytzele
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_course

Read-onlyIdempotent

Retrieve one course's Bulletin record—description, units, grading, GE areas, prerequisites, cross-listings, and courses that require it—so students can see what skipping or delaying it affects.

Instructions

Full Bulletin record for one course: description, units, grading, GE areas, prereq (raw text + parsed tree + status), paired/cross-listed links, source_page, and unlocks: courses whose prereqs name it (as a requirement or one of the alternatives), so a student sees what skipping or delaying it holds up. A '*' after a prereq item means registration enforces it; items without one may be enforced by the instructor up to the end of add/drop (p.2436).

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": {
      "code": "<code>"
    },
    "name": "get_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile needs no repetition. The description instead adds substantive behavior the annotations cannot: the derived `unlocks` computation (reverse prereq lookup, including alternative satisfaction) and the domain rule that a '*' after a prereq item means registration-enforced versus instructor-enforced through add/drop.

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?

Front-loaded with the core purpose, then a compact field enumeration where each item is informative rather than filler. It is dense with parentheticals and the trailing '*' note is a detail an agent may not need at call time, but no sentence is truly wasted.

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 so thoroughly, listing every field the agent can expect. The remaining gap is input-side: the course-code format and error behavior for an unknown code are left unspecified for a tool whose only failure mode is a bad identifier.

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

Parameters2/5

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

Schema coverage is 0% — the lone `code` property carries only `type: string`. The description never states the expected format (e.g. 'CS 101' vs 'CS101'), whether it is case/space sensitive, or what a bad code yields, so the single parameter that every call depends on remains ambiguous.

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 names a specific verb+resource ('Full Bulletin record for one course') and enumerates the exact return contents: description, units, grading, GE areas, prereq tree, cross-listed links, source_page, and unlocks. The phrase 'one course' and 'full record' implicitly but clearly separates it from the list-oriented sibling 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 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 drill-down for a single course from the 'one course' framing and from the mention that `unlocks` shows what skipping it holds up. However, no sibling is named — nothing tells the agent when to prefer get_sections or get_prereq_chain, and no prerequisites or failure conditions are stated.

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

Deploy Server

Other Tools