Skip to main content
Glama
Sign In
GatorPath

GatorPath

by ashleytzele
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

import_dpr

Read-onlyIdempotent

Reads a student's Degree Progress Report PDF locally to return a structured profile, remaining requirements, and DPR vs. GatorPath audit discrepancies.

Instructions

Read the student's Degree Progress Report on their own machine (Student Center → Degree Progress Report, printed to PDF; click Expand All and View All on long lists first) and return a ready profile (completed SF State and transfer courses, in_progress, ge_done, dpr_met substitutions, gpa, catalog_year from the DPR's "Requirement (Catalog) Term") plus remaining: what the DPR itself says is still needed, and cross_check: where GatorPath's audit disagrees with the DPR (the DPR wins). Name, ID and the PDF text never leave this tool, so the student doesn't need to attach the PDF to the chat; ask for the file's path. Add qr_pathway, goal and start_term, then use the profile with the other tools.

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": {
      "pdf_path": "<pdf_path>"
    },
    "name": "import_dpr"
  }
}

Input Schema

NameRequiredDescriptionDefault
pdf_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/closed-world, yet the description adds real behavioral context beyond them: the privacy guarantee that name, ID and PDF text never leave the tool, the precedence rule for conflicting audits, and the requirement to pre-expand lists before printing. These are exactly the kinds of facts an agent cannot infer from the annotations.

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?

Purpose and the three outputs are front-loaded, and each sentence carries useful information (prep steps, privacy, precedence, next steps). The middle sentence is long and parenthetical-heavy, so it is dense but not padded.

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?

With no output schema, the description carries the burden of explaining returns and does so precisely, naming the profile fields and the two auxiliary objects. Combined with the privacy and precedence notes, an agent has everything needed to call and use the result.

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

Parameters4/5

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

Schema coverage is 0% for the single string parameter, but the description compensates by clarifying that it is a file path on the student's own machine and instructing the agent to ask for it. That resolves the main ambiguity (local path vs. attachment) even though no format example is given.

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?

States a specific verb (read/import) and resource (the student's Degree Progress Report PDF) and enumerates the three return values (profile, remaining, cross_check). It is clearly distinct from the sibling import_transcript, which handles a different artifact.

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

Usage Guidelines4/5

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

Gives explicit preparation steps (Expand All and View All, print to PDF) and a follow-on workflow (add qr_pathway, goal, start_term, then use the profile with the other tools), plus the tie-break rule that the DPR wins over GatorPath's audit. It stops short of explicitly contrasting itself with import_transcript, so it is clear but not fully exhaustive on alternatives.

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