Skip to main content
Glama

convert_gpa

Convert a grade from any of 13 African grading systems to the international 4.0 GPA scale used by scholarship applications worldwide. Covers all 54 African countries. Also returns the grade class (e.g. 'First Class Honors') and how the GPA is interpreted in Germany, UK, France, USA/Canada, Australia, Netherlands, and Japan/Korea/China.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gradeYesThe grade class or value. For class-based systems use: 'first_class', 'second_upper', 'second_lower', 'third_class', 'pass'. For kenyan letter grades: 'A', 'B+', 'B', 'C+', 'C', 'D'. For percentage systems: '75%', '68', etc. For french_20: 'tres_bien', 'bien', 'assez_bien', 'passable'. For spanish_10: 'matricula', 'notable', 'aprobado'.
scaleYesGrading system. nigerian=5.0 scale, kenyan/ghanaian/ethiopian/west_african_4=letter/class, south_african=percentage, tanzanian/ugandan=5.0 class, zimbabwean/rwandan/percentage=%, french_20=20-point (26 Francophone+Lusophone countries), spanish_10=10-point (Equatorial Guinea).

TDQS

A4.6/5.0
Behavior4/5

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

Discloses return values including grade class and interpretations across multiple countries. No annotations provided, but description sufficiently covers behavioral aspects for a read-only conversion tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler. First sentence states core action, second adds return details. Efficient and front-loaded.

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?

Given the complexity (13 systems, multiple countries), the description is complete. No output schema, but description explains returns sufficiently.

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 100% with detailed descriptions, and the description adds context like 'Covers all 54 African countries' and examples of grade values. Adds real-world understanding beyond schema.

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?

Clearly states verb 'convert' and resource 'grade' from 13 African grading systems to international 4.0 GPA. Distinguishes from sibling tools which are about visas, costs, and scholarships.

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?

Indicates usage for scholarship applications worldwide. Does not explicitly state when not to use, but siblings are unrelated, making context clear.

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.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool serves a distinct function: visa checks, GPA conversion, cost estimation, scholarship lookup (specific), matching, and searching. There is clear separation between search and get/match, and between cost, visa, and GPA utilities.

Naming Consistency5/5

All tools use a clear verb_noun pattern: check_visa, convert_gpa, estimate_study_costs, get_scholarship, match_scholarships, search_scholarships. The verbs accurately describe the action, and nouns are the domain objects. Perfect consistency.

Tool Count5/5

Six tools is an ideal size for a specialized education/scholarship assistant. Each tool covers a core need without redundancy, and the count is well within the sweet spot for agent usability.

Completeness4/5

The toolset covers the core pre-application workflow: checking visa feasibility, converting GPA, estimating costs, and finding/matching scholarships. The main gap is lack of direct scholarship application or document submission tools, but those are likely outside the server's scope (it's a research/planning assistant).

Resources