Skip to main content
Glama

get_grade_mappings

Get the grade-to-GPA mapping bands for one grading system.

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": {
      "grading_system_id": "<grading_system_id>"
    },
    "name": "get_grade_mappings"
  }
}

Input Schema

NameRequiredDescriptionDefault
grading_system_idYesgrading_systems id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/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. "Get" implies a read, but it says nothing about error behavior for an unknown grading_system_id, whether bands are returned in ascending order, or how many rows to expect. For a no-annotation tool this is thin disclosure.

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?

One short sentence with the key scope constraint front-loaded and no wasted words. It is efficient, though it leaves no room for the guidance the tool lacks.

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?

A simple one-parameter read tool with full schema coverage and no output schema, so the description only needs to convey purpose and return shape. It conveys purpose and roughly what is returned, but omits failure modes and result structure.

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% and the single parameter is documented as "grading_systems id." The description's phrase "for one grading system" reinforces that the ID scopes to a single system's bands, but adds no format or validity detail beyond the schema.

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: "Get the grade-to-GPA mapping bands," scoped to "one grading system." An agent knows exactly what data comes back. It does not, however, distinguish itself from siblings like resolve_grading_scale, convert_grade, or calculate_gpa, which sound adjacent.

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 guidance and no named alternative. With siblings such as resolve_grading_scale and convert_grade in the catalog, the agent must infer on its own whether this is the lookup for raw band definitions versus a conversion call.

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.