Skip to main content
Glama

Activate Semester Pass

activate_semester_pass
DestructiveIdempotent

Activate a paid Semester Pass — the student supplies their phone (for pickup-day reminders), dorm building + room, and their CHOSEN PICKUP DAY (one of the campus's availablePickupDays from list_campuses). Only callable on a pass in PENDING_ACTIVATION status (i.e. payment has cleared). After activation, weekly pickup Orders auto-generate on the chosen day until the term ends. Activation is idempotent — re-calling on an already-ACTIVE pass is a no-op.

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>",
      "studentPhone": "<studentPhone>",
      "dormBuilding": "<dormBuilding>",
      "dormRoom": "<dormRoom>",
      "studentPickupDay": "<studentPickupDay>"
    },
    "name": "activate_semester_pass"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesPass code (FSP-XXXXXX).
dormRoomYesRoom number (e.g. "412B").
dormBuildingYesDorm building name (e.g. "Sproul Hall", "De Neve Plaza").
studentPhoneYesStudent phone in E.164 format (+1XXXXXXXXXX) or US 10-digit.
studentPickupDayYesPickup day of week — 0=Sun, 1=Mon, …, 6=Sat. Must be one of the campus's availablePickupDays from list_campuses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare idempotentHint and openWorldHint, so the idempotency/'no-op' sentence is partly redundant, but the description adds real behavioral context beyond the annotations: the status gate, and the side effect that 'weekly pickup Orders auto-generate on the chosen day until the term ends.' What it does not clarify is why destructiveHint=true when activation is described as a reversible no-op on re-call — a mismatch left unexplained.

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 action and required inputs, then the precondition, then side effects — a sensible order with little waste. It is dense (long parentheticals, several clauses per sentence) but each clause carries substantive information.

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?

For a mutating 5-param tool with no output schema, the description covers the critical gaps: entry-state precondition, cross-tool dependency for valid pickup days, and downstream effects. It stops short of error behavior (what happens if the pass is not PENDING_ACTIVATION) and does not explain the destructiveHint implication.

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 100%, so the schema already documents all five parameters including the 0-6 day encoding and the list_campuses constraint. The description adds only the rationale for studentPhone ('for pickup-day reminders') and does not add format or validation detail beyond the schema, so the baseline of 3 applies.

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 and resource ('Activate a paid Semester Pass') and immediately names the state transition (PENDING_ACTIVATION → ACTIVE) plus the resulting behavior. This clearly separates it from buy_semester_pass (purchase) and get_semester_pass (retrieval) among the siblings.

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 an explicit precondition — 'Only callable on a pass in PENDING_ACTIVATION status (i.e. payment has cleared)' — and directs the agent to list_campuses for valid pickup days. It does not explicitly name the prerequisite sibling (buy_semester_pass) as the step that precedes it, so routing is implied rather than spelled out.

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