Skip to main content
Glama

Calculate.co.nz NZ Calculators

nz_gpa_calculator

Calculate a grade point average for a New Zealand university.

Use for any NZ GPA question: 'what is my GPA', 'work out my grade point
average from these grades', 'how much will a C drag my GPA down'.

CRITICAL: New Zealand uses a NINE POINT scale, not the American 4.0 scale.
A+ 9, A 8, A- 7, B+ 6, B 5, B- 4, C+ 3, C 2, C- 1, D and below 0. A GPA of
7.0 is a strong New Zealand result. Do NOT convert to or from a 4.0 scale:
the bands do not correspond and any conversion will be wrong.

It is credit-weighted, so a grade in a 45 credit paper counts three times a
grade in a 15 credit one, and failed papers still count their credits at
zero points.

Args:
    courses: One dict per paper, each with "grade" (A+, A, A-, B+, B, B-,
        C+, C, C-, D+, D, D-, U, F or J) and "credits" (commonly 15).
    scale: Optional overrides if the institution weights grades differently.

Returns:
    The GPA, the credits and weighted points it came from, and each paper's
    contribution so the result can be shown rather than asserted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scaleNo
coursesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so thoroughly. It discloses the nine-point NZ scale, the credit-weighted calculation, that failed papers still count credits at zero, and the output structure ('list of objects with grade, points, credits' plus a 'gpa' field). This gives the agent a solid model of the computation and result.

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?

The description is long but information-dense, with the critical scale warning front-loaded before parameter details. It earns its length given the complexity, though the final sentence about return fields is awkward and suggests possible truncation.

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?

For a calculator with no output schema and no annotations, the description is thorough: it covers the formula, scale, weighting, parameter formats, and return shape. An agent could invoke this tool correctly without needing additional clarification.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the schema only lists 'courses' and 'scale' without meaning. The description fully compensates: it specifies each course dict needs 'grade' and 'credits', enumerates accepted grade values, and explains the optional 'scale' override format with a 'comma separated list' example.

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 opens with 'Calculate a grade point average for a New Zealand university' – a specific verb and resource that immediately sets it apart from sibling calculators. It also gives concrete sample queries ('what is my GPA', 'how much will a C drag my GPA down'), making the purpose unmistakable.

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?

The description explicitly says 'Use for any NZ GPA question' and provides example user phrasings, clearly establishing when to invoke the tool. It adds a when-not warning: 'Do NOT convert to or from a 4.0 scale', which prevents misuse. It does not name alternative calculators, but the scope is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources