Skip to main content
Glama

get_us_equivalent

Convert grade points on any scale to a US GPA, with letter grade and honours classification.

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": {
      "grade_points": "<grade_points>"
    },
    "name": "get_us_equivalent"
  }
}

Input Schema

NameRequiredDescriptionDefault
mappingsNoGrade mappings to use directly, instead of the database
min_passNoSource scale pass mark
max_scaleNoSource scale maximum (default 4)
grade_pointsYesGrade points on the source scale
grading_system_idNograding_systems id whose bands set the US equivalent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the return payload (US GPA plus letter grade and honours classification), which matters because there is no output schema, but it says nothing about how the conversion resolves the source scale, what happens when grading_system_id is omitted, or any failure/precision behavior.

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?

A single tight sentence with the core action front-loaded and the outputs appended. No filler or redundant restatement of the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter conversion tool with no output schema, the description covers the purpose and the shape of the result but omits the operational detail an agent needs for correct invocation: which lookup source wins, what the default scale assumption is, and what a returned classification means. Adequate but with clear gaps.

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 coverage is 100%, so every parameter is already documented in the schema, establishing the baseline of 3. The description's phrase 'on any scale' adds only a small hint that the tool is scale-agnostic; it does not explain the precedence between the mappings array and grading_system_id, or the role of max_scale/min_pass.

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+resource: converting grade points on an arbitrary scale into a US GPA, and it also names the secondary outputs (letter grade, honours classification). It does not differentiate itself from likely-overlapping siblings such as convert_grade, calculate_gpa, calculate_normalized_gpa, or gpa_to_percentage, so an agent cannot resolve which converter to pick from the description alone.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no alternative is named, despite four sibling tools that plausibly overlap. The agent is left to infer that 'any scale to US GPA' means this is the canonical single-value conversion tool.

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.