Skip to main content
Glama

convert_grade

Convert one grade between two grading systems using the real band-standing logic (Bavarian formula for inverted scales, linear fallback), via the US 4.0 baseline. Give grading-system ids to read bands from the database, or max_scale/min_pass numbers for a numeric conversion.

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": {
      "source_grade": "<source_grade>"
    },
    "name": "convert_grade"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_gradeYesGrade label (e.g. 'A', '8.5', 'First Class') in the source system
source_mappingsNoSource grade mappings to use directly, instead of the database
source_min_passNoSource scale pass mark
target_mappingsNoTarget grade mappings to use directly, instead of the database
target_min_passNoTarget scale pass mark
source_max_scaleNoSource scale maximum (e.g. 10 for India 10-point, 4 for US)
source_system_idNograding_systems id for the source system
target_max_scaleNoTarget scale maximum
target_system_idNograding_systems id for the target system

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does explain the method: Bavarian formula for inverted scales, linear fallback, routed through a US 4.0 baseline. It stops short of stating the return shape (converted grade plus any classification/points), what happens when a grade cannot be placed in the bands, or confirming there are no side effects.

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, zero filler. The core action and algorithm come first, followed immediately by the two input strategies, so the agent gets the operative information before any detail.

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?

For a nine-parameter tool with four alternative input paths and no output schema, the description covers the essential decision of which path to take and how conversion is computed. The remaining gap is the result shape and failure behavior, which no other structured field supplies here.

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 each of the nine parameters is already documented, which sets the baseline at 3. The description does add grouping semantics the schema lacks, namely that source/target pairs are alternatives (system ids OR numeric scale values), but it does not clarify precedence when both mapping arrays and system ids are supplied.

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?

The description states a specific verb and resource: 'Convert one grade between two grading systems.' The word 'one' implicitly scopes it against the GPA/aggregation siblings, but no sibling is named explicitly and the boundary with get_us_equivalent is left for the agent to infer.

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?

It clearly separates two usage modes: pass grading-system ids to read bands from the database, or pass max_scale/min_pass numbers for a purely numeric conversion. That is real decision guidance for input selection, though it offers no exclusions telling the agent when to prefer get_us_equivalent or calculate_normalized_gpa instead.

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.