Skip to main content
Glama

Class schedule

get_schedule
Read-onlyIdempotent

Retrieves a student's weekly bell schedule and class period matrix, including teacher, room, and term for each course, so you can see when and where classes meet.

Instructions

The student's schedule: this week's bell schedule by day with times, and the period matrix with teacher, room and term for each class.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
studentNoStudent to use: name, or index from list_students. Defaults to PS_DEFAULT_STUDENT, else the student PowerSchool shows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered structurally. The description contributes genuinely useful content about what is returned (bell schedule times plus a per-class teacher/room/term matrix), which matters because there is no output schema. It does not say what happens with no active term, whether the student parameter is required, or how 'this week' is resolved.

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?

A single front-loaded sentence that leads with the resource and then enumerates the returned parts. Every clause carries information (by day, with times, teacher/room/term); nothing is padded or redundant.

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 one optional parameter, full schema coverage and no output schema, the description needs to convey the return shape — and it does, naming both the bell schedule and the period matrix with their fields. Remaining gaps (term selection, empty-schedule behavior, how the current week is determined) are modest for a read-only lookup 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?

Schema description coverage is 100% and the single `student` parameter already documents its name-or-index form and the PS_DEFAULT_STUDENT fallback. The description adds no further meaning about the parameter, so the baseline of 3 applies — the schema does all the work here.

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 uses a specific resource framing ("The student's schedule") and enumerates the two returned artifacts: this week's bell schedule by day with times, and the period matrix with teacher, room and term per class. That is far more informative than a restatement of the name. It stops short of naming a sibling to contrast with (e.g. get_class_scores or get_attendance), so it is clear but not sibling-differentiated.

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 'what classes does this student have and when', partly from the "this week's" temporal scoping. There is no explicit when-to-use statement, no exclusion of lookalike siblings, and no note about prerequisites or what to do if no schedule is configured.

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