Skip to main content
Glama
Sign In
GatorPath

GatorPath

by ashleytzele
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

import_transcript

Read-onlyIdempotent

Parse a saved unofficial transcript PDF locally to extract completed and in-progress courses, grades, units, and terms for academic planning.

Instructions

Read the student's SF State unofficial transcript PDF on their own machine (Student Center → Unofficial Transcript, saved as a PDF) and return only course codes, grades, units and terms: completed, in_progress, transfer_units. Name, ID, birthdate 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 instead. Merge the result into the profile. Transfer courses show as totals only: their requirements come from the DPR.

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_transcript"
  }
}

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?

Beyond the supplied annotations, it discloses local processing and data minimization: name, ID, birthdate, and full PDF text never leave the tool, while only the specified course data is returned. It also explains that transfer courses appear only as totals; the instruction to merge the result is post-processing guidance rather than a clear claim that this tool itself writes the profile.

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?

The description is front-loaded with its purpose, and each subsequent sentence adds distinct invocation, privacy, workflow, or scope information. It is dense but contains no substantive filler.

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?

It covers document provenance, input acquisition, returned data categories, sensitive-data handling, and transfer-credit limitations, which is substantial given the absence of an output schema. The exact result structure and behavior for unreadable, incorrect, or unsupported PDFs remain unspecified.

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?

Although the schema gives pdf_path no description, the text establishes that the input is a path to a locally saved Student Center unofficial-transcript PDF and that the PDF should not be attached to the chat. It does not explicitly name pdf_path or specify path syntax, but it nearly compensates for the 0% schema coverage for this single required string.

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 opening sentence specifies the operation and resource: reading a local SF State unofficial transcript PDF and extracting course codes, grades, units, and terms into completed, in_progress, and transfer_units. The closing limitation concerning DPR-based requirements also helps distinguish transcript import from DPR handling.

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?

It provides a concrete workflow: obtain the PDF from Student Center, ask for its path rather than an attachment, merge the result into the profile, and rely on the DPR for transfer requirements. It would be stronger if it explicitly routed those steps to save_profile and import_dpr or stated when transcript import is unnecessary.

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