Skip to main content
Glama

Class assignments and scores

get_class_scores
Read-onlyIdempotent

Retrieve a student's assignment scores for one class and term, including points possible, percentages, due dates, categories, and missing, late, exempt, or collected flags.

Instructions

Assignments for one class with score, points possible, percent, due date, category and flags (missing, late, exempt, collected). course matches by fuzzy name or period number (e.g. "bio", "3", "period 3"). term is a grade column such as P1 or S1 (default: the current term). Stored-only terms (E1, E2, S2 once closed) usually return nothing.

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": {
      "course": "<course>"
    },
    "name": "get_class_scores"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNoGrade column, e.g. P1, S1. Default: current term
courseYesClass name (fuzzy) or period number
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

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds behavior beyond that: the returned field set, fuzzy matching on `course`, the current-term default, and the caveat that closed/stored-only terms yield empty results. It does not address ambiguous fuzzy matches or what happens when multiple classes match.

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?

Three dense sentences, front-loaded with what the tool returns before drilling into parameter quirks. Minor waste from restating the term default already present in the schema, but no filler or marketing language.

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 correctly compensates by listing the returned fields, and it covers the two parameters most prone to misuse. The unmentioned `student` parameter and the absence of any ambiguity-handling note for fuzzy course matching are the remaining gaps for a tool whose results are student-specific.

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 100%, so baseline is 3, but the description earns above that by giving concrete `course` examples ('bio', '3', 'period 3') and explaining the term semantics including the empty-result gotcha. It says nothing about the `student` parameter, so that one relies entirely on the schema.

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 names the resource precisely (assignments for one class) and enumerates exactly what comes back: score, points possible, percent, due date, category and flags. That is far more specific than the title alone. It does not, however, distinguish itself from siblings like get_grades, get_missing or get_grade_history, leaving the agent to infer the boundary.

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?

Usage context is clear: `course` accepts a fuzzy name or period number, `term` defaults to the current term, and stored-only terms (E1, E2, S2 once closed) 'usually return nothing' — an explicit when-not-to-expect-results warning. No alternative tool is named for the missing/late-only or historical cases, so it stops short of full routing guidance.

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