Skip to main content
Glama

Estimate GPA

estimate_gpa
Read-onlyIdempotent

Calculates an estimated 4.0-scale GPA from stored term grades, credit-hour weighted, with optional +1 weighting for AP or Honors courses; not an official district GPA.

Instructions

ESTIMATED GPA computed locally from stored term grades on a 4.0 scale (A=4.0 ... F=0, plus/minus steps), credit-hour weighted. With weighted=true, courses whose name contains AP or Honors get +1. This is an estimate, NOT the official GPA: the district's own scale, course weights and rounding may differ.

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": "estimate_gpa"
  }
}

Input Schema

NameRequiredDescriptionDefault
studentNoStudent to use: name, or index from list_students. Defaults to PS_DEFAULT_STUDENT, else the student PowerSchool shows.
weightedNoAdd +1 for courses with AP or Honors in the name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description still adds real behavioral context: the computation is done locally from stored term grades, the exact weighting rule when weighted=true, and an explicit accuracy disclaimer about district scale and rounding differences. It does not explain the return shape (single number vs per-course breakdown), which is the remaining gap.

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 tight sentences, front-loaded with the core definition and ending with the caveat, with no filler. The parenthetical scale enumeration is dense but earns its place by making the scale explicit.

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 two-parameter read-only computation with no output schema, the description covers source data, scale, weighting, and reliability limits — enough to call it correctly. Only the return format (single GPA value vs breakdown) is left implicit, a minor omission given the tool's simplicity.

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 both parameters are already documented there, including the AP/Honors +1 rule that the description restates. The description adds only the fact that the bump is capped to the weighted flag rather than applying globally. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

The description names a specific computed artifact (estimated GPA), the exact input source (stored term grades), and the scale (4.0, A=4.0 ... F=0, plus/minus steps, credit-hour weighted). It also distinguishes the output from the official GPAs elsewhere in the ecosystem, so an agent can tell it is not the same as raw grade retrieval.

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 rather than stated: the caveat 'This is an estimate, NOT the official GPA' tells the agent what the number is good for, but it never says when to pick this over get_grades, get_class_scores, or what_if_grade, nor any prerequisites. Adequate context, no explicit when/when-not routing.

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