Skip to main content
Glama

calculate_gpa

Calculate a weighted GPA from courses (grade, credits, weight regular/honors/ap/ib), optionally resolved against a grading system in the database using the real band logic.

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": {
      "courses": "<courses>"
    },
    "name": "calculate_gpa"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNoScale to report the GPA on (default 4.0)
coursesYes
grading_system_idNograding_systems id whose bands resolve course grades

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose two behaviors beyond the schema: that weighting is applied per course weight category and credits, and that grades can be resolved through database grading-system bands. It stops short of saying what happens when grading_system_id is omitted, how unresolvable grades are handled, or what the returned value looks like, and "the real band logic" is unhelpful phrasing rather than a specification.

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?

A single front-loaded sentence covering the verb, the inputs, and the optional database path with no padding. The trailing clause "using the real band logic" is vague enough to be spent wording.

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 tool taking a nested course array, three parameters, and an enum scale, the description covers the core computation but omits the default/fallback path when no grading system is supplied and, with no output schema, never indicates what shape the GPA result takes. Adequate to call the tool, not complete enough to predict its behavior confidently.

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 67%, so the schema already documents scale, grade, and grading_system_id. The description restates the course fields and clarifies that grading_system_id resolution is optional, but adds no detail on scale selection, weight-vs-credits interaction, or accepted grade string formats beyond what the schema states.

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 ("Calculate a weighted GPA from courses") and enumerates the inputs and weight categories it handles, so the operation is immediately legible. It does not distinguish itself from the sibling calculate_normalized_gpa or resolve_grading_scale, so an agent cannot tell from this text alone which calculator to pick.

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

Usage Guidelines3/5

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

The phrase "optionally resolved against a grading system in the database" implies when to supply grading_system_id, which is a useful conditional cue. However, there is no explicit when-to-use/when-not-to-use guidance and no routing against the closely related calculate_normalized_gpa or resolve_grading_scale siblings.

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.