Skip to main content
Glama

Calculate.co.nz NZ Calculators

nz_ncea_grade_calculator

Work out an NCEA result: credits, the co-requisite, the certificate, endorsements and UE, on NZQA's Assessment Rules 2026.

Use for: 'have I passed NCEA level 2', 'how many credits do I need for
NCEA', 'NCEA literacy and numeracy co-requisite', 'NCEA merit
endorsement', 'how many credits for excellence endorsement', 'course
endorsement NCEA', 'do I have University Entrance', 'NCEA calculator'.

60 CREDITS AT THE LEVEL OR ABOVE, PLUS THE CO-REQUISITE (10 LITERACY AND
10 NUMERACY, MET ONCE FOR EVERY LEVEL). NZQA's "80 credits" is 60 + 20.
The old rule of 80 credits alone is gone: 80 credits with no co-requisite
is not a certificate. Ask whether the co-requisite is met; if it was met
in an earlier year, or under the old rules in 2023 or earlier, pass 10
and 10. Do not put co-requisite credits in subjects.

50 GAINS A CERTIFICATE ENDORSEMENT, AND 49 DOES NOT, BUT ONLY WITH THE
CERTIFICATE. Excellence: 50 Excellence credits. Merit: 50 at Merit OR
Excellence, so Excellence credits count towards Merit. With 50 credits
but no certificate, *_endorsement_credits_met is true and
*_endorsement_earned is false: say it is awarded once the level is.

COURSE ENDORSEMENT IS 14 CREDITS IN ONE COURSE: Excellence at Excellence,
Merit at Merit or above, Achieved at any grade.

UE (LEVEL 3 ONLY): NCEA Level 3, three approved subjects each with 14+
credits, literacy of 5 reading AND 5 writing (not 10 in total), and 10
numeracy credits. Say which requirement is missing.

Not checked: the level of each standard, and the 3 internal and 3
external credits a course endorsement needs in most courses. New
qualifications replace NCEA from 2028 and are not modelled. For a rank
score, use nz_ncea_rank_score_calculator.

Args:
    level: 1, 2 or 3.
    subjects: List of {"name", "achieved", "merit", "excellence",
        "ue_approved"}; credits that count towards the 60, whole numbers;
        ue_approved is for Level 3 subjects on NZQA's approved list.
    ue_literacy_reading_credits: Level 3: Level 2+ reading credits on the UE list.
    ue_literacy_writing_credits: Level 3: Level 2+ writing credits on the UE list.
    ue_numeracy_credits: Level 3: UE numeracy credits.
    literacy_corequisite_credits: literacy co-requisite credits (need 10).
    numeracy_corequisite_credits: numeracy co-requisite credits (need 10).

Returns:
    Totals by grade, whether the 60 and the co-requisite are met, whether
    the level is achieved and what is missing, both certificate
    endorsements with credits still needed, each course endorsement, and
    University Entrance at Level 3.

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": {
      "level": "<level>",
      "subjects": "<subjects>"
    },
    "name": "nz_ncea_grade_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYes
subjectsYes
ue_numeracy_creditsNo
ue_literacy_reading_creditsNo
ue_literacy_writing_creditsNo
literacy_corequisite_creditsNo
numeracy_corequisite_creditsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description must carry the full burden and it does: it names the ruleset version (Assessment Rules 2026), explains the 60+co-requisite logic versus the obsolete "80 credits" rule, and gives edge-case handling (co-requisite met in an earlier year, or under 2023-or-earlier rules, pass 10 and 10). It also states explicitly what is NOT modelled, which prevents false confidence in the output.

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?

It is front-loaded with purpose and use cases, and the paragraph structure maps cleanly onto the domain requirements. It is long, however, with ALL-CAPS rule blocks and some restatement, e.g. the 50-credits-but-no-certificate case is spelled out twice across the endorsement paragraph, costing space without adding information.

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 7-parameter, rule-heavy calculator with no output schema, the description closes every gap an agent needs: the domain thresholds, the asymmetry between *_endorsement_credits_met and *_endorsement_earned, the UE sub-requirements (5 reading AND 5 writing, not 10 total), and a "Returns" summary of what comes back. Nothing essential to calling or interpreting it is missing.

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 description coverage is 0% and the schema only supplies bare titles, yet the "Args:" section defines every parameter's meaning: level is 1/2/3, subjects carry a named inner structure (name, achieved, merit, excellence, ue_approved) whose credits count towards the 60, and each optional credit field is annotated with its threshold ("need 10") and eligibility scope ("Level 2+ reading credits on the UE list"). This fully compensates for the undescribed nested items object.

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?

"Work out an NCEA result: credits, the co-requisite, the certificate, endorsements and UE" gives a specific verb plus an enumerated set of resources. It also explicitly routes the sibling case away ("For a rank score, use nz_ncea_rank_score_calculator"), so an agent can separate it from nz_ncea_rank_score_calculator without reading either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The "Use for:" block lists concrete user phrasings ("have I passed NCEA level 2", "do I have University Entrance") covering the exact lookup intents this tool serves. It also names the alternative tool for rank scores and states what is out of scope (standard levels, internal/external credit split, post-2028 qualifications).

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