Skip to main content
Glama
Sign In
GatorPath

GatorPath

by ashleytzele
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_program_requirements

Read-onlyIdempotent

Retrieve a program's requirement groups and shared bachelor's graduation requirements—GE areas, SF State Studies, American Institutions, GWAR, and unit/residence/GPA totals—for a catalog year.

Instructions

A program's requirement groups (as written in its rules YAML, each with its Bulletin page) plus the university graduation requirements every bachelor's degree shares: GE areas, SF State Studies, American Institutions, GWAR, unit/residence/GPA totals. catalog_year: the student's (e.g. 'Fall 2025' or '2025-26'); default the newest.

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": {
      "program": "<program>"
    },
    "name": "get_program_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
programYes
catalog_yearNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavioral context: the response is composite, mixing program-specific requirement groups (each carrying a Bulletin page reference) with university-wide graduation requirements that every bachelor's degree shares.

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?

Two sentences, front-loaded with what is returned, then the parameter detail. The first sentence is long and stacks a parenthetical plus a six-item list, but every element is substantive and nothing is redundant.

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?

With no output schema, the description does the necessary work of describing return contents at a summary level, which is the right call. It still leaves gaps for a two-parameter lookup tool: how to supply or discover a valid program value, and what happens when a program or catalog year does not exist.

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 carry both parameters. It handles catalog_year well, giving two example formats ('Fall 2025', '2025-26') and the newest-by-default rule. The required 'program' parameter gets no clarification at all — no indication whether it is a name, code, slug, or how to obtain it.

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 a specific resource and its full scope: a program's requirement groups from its rules YAML plus the shared university-wide requirements (GE areas, SF State Studies, American Institutions, GWAR, unit/residence/GPA totals). That enumeration makes it clearly distinct from list_programs or audit_progress, though it never names a sibling to contrast with.

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 tool for fetching a program's requirement structure, and 'default the newest' gives a directive for catalog_year. There is no explicit statement of when to choose this over audit_progress or compare_programs, nor any prerequisite such as resolving the program identifier first.

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