Skip to main content
Glama

Get Semester Pass

get_semester_pass
Read-onlyIdempotent

Look up a Fold Semester Pass by code (FSP-XXXXXX). Returns current status, campus, term, dorm details (if claimed), and whether it's ready for pickups. Use this for "is my pass active yet?" or "what's the status of FSP-XXXXXX?" inquiries.

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

Input Schema

NameRequiredDescriptionDefault
codeYesPass code (FSP-XXXXXX). Case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally. The description adds real behavioral value by specifying the returned payload, including that dorm details appear only 'if claimed' and that readiness-for-pickup is surfaced, which an agent cannot infer from annotations.

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?

Two sentences with no filler: the lookup action and identifier come first, then the return contents, then the use cases. Every clause earns its place.

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 usefully enumerates the fields returned, which is the main thing an agent needs. It is slightly incomplete on failure behavior (invalid or unknown code) but otherwise sufficient for a one-parameter read tool.

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?

Single parameter with 100% schema description coverage, so the schema already documents the format and case-insensitivity. The description restates the FSP-XXXXXX shape but adds no new semantics about the parameter.

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?

Specific verb (look up) plus specific resource (Fold Semester Pass) with the identifier format and an enumeration of returned fields. The read-only 'look up' framing clearly separates it from siblings like activate_semester_pass and buy_semester_pass without needing to name them.

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 concrete triggering inquiries ("is my pass active yet?", "what's the status of FSP-XXXXXX?"), which is clear usage context. It does not explicitly rule out cases or point at alternatives such as activate_semester_pass when the pass exists but is inactive, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources