GPA Calculator MCP

Convert a GPA to another scale

convert_gpa_scale

Read-only

Translates a GPA from one grade scale to the nearest band on another, helping compare a US GPA with UK classifications or Australian grades.

Instructions

Convert a GPA on one grade scale to the nearest band on another, so a GPA from one country can be read as a UK class or an Australian grade. Inputs: gpa (the GPA to convert, 0 to 7 and at or below the top of from_scale), from_scale (the scale the GPA is on, default us4) and optional to_scale (the scale to convert to; leave it out to convert to both the uk-classification and australia-hd scales). The GPA is read as a share of the top grade point on its own scale, then the nearest band on the target scale is returned with its percentage range and grade points. This is a common comparison, not an official conversion, so check the target school's table. Example prompt: "I have a 3.5 GPA on the US 4.0 scale. What is that in the UK?"

Input Schema

Name	Required	Description	Default
`gpa`	Yes	The GPA to convert, between 0 and 7. It must be at or below the top grade point of from_scale.
`to_scale`	No	Grade scale id to convert to: "us4", "us4plus", "ontario-college", "uk-classification", "australia-hd" or "weighted-5.0". Leave it out to convert to both the uk-classification and australia-hd scales.
`from_scale`	No	Grade scale id the GPA is on: "us4", "us4plus", "ontario-college", "uk-classification", "australia-hd" or "weighted-5.0". Defaults to "us4".	us4

Output Schema

Name	Required	Description
`gpa`	Yes	The GPA that was converted.
`from_scale`	Yes	The scale id the GPA was on.
`conversions`	Yes	One entry per target scale, in the order they were converted.
`from_max_points`	Yes	The top grade point of the scale the GPA was on.
`from_scale_name`	Yes	The name of the scale the GPA was on.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.7Oct 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the conversion method (GPA read as a share of the top grade point, nearest band chosen) and the important caveat that this is a comparison, not an official conversion. That is meaningful added context; only rate limits or precision/rounding edge cases are left unmentioned.

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?

Front-loads the purpose and the input list, then the mechanics and caveat, then the example. Slightly overlong — the example prompt and restating the parameter names cost some words — but nothing is truly wasted.

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?

An output schema exists, so return values need not be spelled out, yet the description still states the band/percentage/grade-point shape, which is helpful. For a three-parameter read-only converter this is essentially complete; only sibling disambiguation is missing.

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%, so every parameter is already documented, including the enum values, the from_scale default and the dual-output behavior when to_scale is omitted. The description restates those facts nearly verbatim rather than adding new semantics, so the baseline 3 applies.

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 verb and resource (convert a GPA between grade scales) plus the concrete outcome (nearest band with percentage range and grade points). It does not distinguish itself from the sibling 'convert_grade', which an agent could easily confuse with this one, so it falls short of a 5.

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?

Gives a clear motivating context (reading a GPA from one country as a UK class or Australian grade) and an example prompt, and explicitly explains the omitted-to_scale case. It names no alternatives or exclusions, so it never tells the agent when to prefer 'convert_grade' or 'target_gpa_planner' instead.

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

Deploy Server