Skip to main content
Glama
Sign In

SmartTools

by io.github.9thShini
OverviewDiscussionsAdmin

GPA calculator

gpa_calculator

Weighted grade point average from letter grades (US 4.0 scale, +/-) or numeric grade points and credit hours. Runs on smart-tools.xyz.

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": "gpa_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage for the source_url link (default en)
coursesYesEach course as { grade, credits }. grade is a letter (A, A-, B+ …) or numeric grade points (0–4.5); credits defaults to 1.

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?

With no annotations, the description carries the burden of behavioral disclosure. It explains the core computation and accepted input types, but omits details such as how invalid grades are handled, rounding behavior, or the response format. This is adequate but not rich.

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?

The description is a single sentence and front-loaded with the core purpose. The trailing 'Runs on smart-tools.xyz' is extraneous and does not serve the agent, slightly reducing conciseness.

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?

The tool has two parameters (one nested array), no annotations, and no output schema. The description explains inputs and scale but does not state what the tool returns (e.g., a numeric GPA, JSON, or display format). For a simple calculator, this is a notable gap but not fatal.

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 the description need not repeat parameter details. It does add context about the US 4.0 scale and plus/minus, which aligns with the 'grade' parameter, but it does not go beyond the schema's descriptions. Baseline score of 3 is appropriate.

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?

The description clearly states the tool computes a 'weighted grade point average' from letter grades or numeric grade points with credit hours. It specifies the US 4.0 scale and +/- grading, which distinguishes it from other calculator tools in the sibling list.

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?

The description does not mention when to use this tool instead of alternatives, nor any exclusions or prerequisites. The phrase 'Runs on smart-tools.xyz' is irrelevant for usage guidance. There is no explicit context like 'Use for academic GPA calculations'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SmartTools toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources