Skip to main content
Glama

Current grades

get_grades
Read-onlyIdempotent

Retrieve a student's current letter grades and percentages for every class in the active term, including absences and tardies, and list other terms with existing grades.

Instructions

Current letter grade and percent for every class in the active term (from the PowerSchool home page), plus absences and tardies. Also lists the other terms with any grade they already have.

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

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

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is fully covered. The description contributes the data scope (grades plus absences/tardies plus a trailing list of other terms), but says nothing about freshness, ordering, or failure behavior when the student has no active term.

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?

Two sentences, front-loaded with the primary payload before the secondary ones, with no filler. The trailing clause ('Also lists the other terms with any grade they already have') is slightly awkward but still carries 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?

There is no output schema, so the description has to sketch the return shape, and it does: letter grade, percent, per-class, plus absences, tardies, and other-term grades. What is missing is minor formatting detail (how terms and classes are labeled), which is unlikely to change tool selection.

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?

Only one optional parameter, and the schema already documents it at 100% coverage, including the PS_DEFAULT_STUDENT fallback. The description adds no further meaning about the student selector, so this is the baseline case where the schema does the work.

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 a specific verb-and-resource pair ('current letter grade and percent for every class in the active term') and pins the data source ('from the PowerSchool home page'). It also states secondary payloads (absences, tardies, other terms), which separates it from assignment-level siblings like get_class_scores, though it never names an alternative explicitly and the 'other terms' clause blurs slightly against get_grade_history.

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 implied by scope ('current ... active term') rather than stated: there is no 'use this when...' or 'use X instead for...' sentence. An agent can infer this is the snapshot/overview call versus detail or historical calls, but must do the inferring itself.

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