Skip to main content
Glama

calculate_normalized_gpa

Normalize a raw grade with the SQL calculate_normalized_gpa function (piecewise band match on a grading-system version), with a TypeScript piecewise fallback when the SQL function is unavailable.

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": {
      "raw_grade": "<raw_grade>"
    },
    "name": "calculate_normalized_gpa"
  }
}

Input Schema

NameRequiredDescriptionDefault
raw_gradeYesRaw grade label or number (e.g. 'A', '8.5')
raw_percentNoRaw percentage (0-100), used for numeric band matching
grading_system_idNograding_system_canonical id (resolved to its active version)
grading_system_version_idNograding_system_versions id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/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 a genuinely useful trait, the TypeScript piecewise fallback when the SQL function is unavailable, but says nothing about failure modes such as an unknown grading_system_id, missing version resolution, or ambiguous raw_grade versus raw_percent input.

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

Conciseness3/5

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

It is a single front-loaded sentence, but it spends words naming the SQL function calculate_normalized_gpa, which merely echoes the tool name, and the parenthetical plus fallback clause make it denser than the information warrants.

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

Completeness2/5

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

With no annotations and no output schema, the description should indicate what a 'normalized' result looks like (scale, range, direction of conversion) and what happens on missing grading-system data. Neither is covered, leaving gaps an agent needs in order to call and interpret this tool correctly.

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 all four parameters, including the grading_system_id-to-version resolution note, are already documented in the schema. The description adds no parameter-level meaning, such as precedence between raw_grade and raw_percent or behavior when both system identifiers are passed.

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 concrete verb and object ('Normalize a raw grade') and explains the mechanism ('piecewise band match on a grading-system version'), which is more specific than a restatement of the name. It does not, however, distinguish this from siblings such as calculate_gpa, convert_grade, or get_us_equivalent, so an agent must infer the boundary itself.

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 mention of the sibling tools that also transform grades. The phrase 'piecewise band match on a grading-system version' only implies that a grading system is needed; it never tells the agent when this tool is preferable to convert_grade or calculate_gpa.

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.