Skip to main content
Glama

Grade history

get_grade_history
Read-onlyIdempotent

Retrieve a student's stored final grades for every term PowerSchool has on file—current and prior years—including course, letter grade, percent, citizenship, and credit hours.

Instructions

Stored final grades for every term PowerSchool has on file (current and prior years): course, letter grade, percent, citizenship, credit hours.

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

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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds genuinely new behavior context beyond that: the data is persisted final grades rather than in-progress, and it spans every term PowerSchool has on file including prior years, which tells the agent not to expect a single-term snapshot.

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?

A single front-loaded clause with zero filler; the scope constraint comes first and the field list last. It is a verbless fragment rather than a sentence, but nothing is wasted and no sentence needs deleting.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 must carry the return contract, and it does by naming the five grade fields returned. Combined with full schema coverage for the single optional parameter and annotations covering the read-only safety profile, an agent has everything needed to call this correctly.

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?

There is one optional parameter and schema description coverage is 100%, so the schema already explains the student identifier, its default fallback chain, and list_students indexing. The description adds nothing about the parameter, which is acceptable at full coverage but earns only the baseline.

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?

States a specific resource and scope: stored FINAL grades for every term on file, including prior years, and enumerates the returned fields (course, letter grade, percent, citizenship, credit hours). This implicitly distinguishes it from a current-grades sibling like get_grades, but it never names that sibling, so an agent must infer the split.

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: the words 'stored final grades' and 'current and prior years' suggest this is the historical/transcript-style lookup, while what_if_grade, estimate_gpa and get_grades are left for the agent to reason about. No explicit when-to-use, when-not-to-use, or alternative routing is given.

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