Skip to main content
Glama

resolve_grading_scale

Resolve the applicable grading scale for an institution and/or country: institution override, then country profile, then global default, then a US 4.0 fallback — with confidence and an explanation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "resolve_grading_scale"
  }
}

Input Schema

NameRequiredDescriptionDefault
country_codeNoTwo-letter country code (e.g. IN, DE, US)
institution_idNoinstitutions id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations present, the description carries the burden and does so well: it discloses the exact precedence order (institution override → country profile → global default → US 4.0 fallback), meaning the tool degrades gracefully rather than erroring on unknown inputs. It also states the response includes confidence and an explanation. It omits only minor traits such as read-only nature and whether any external lookup latency applies.

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?

One dense sentence with zero filler, front-loading the action and resource, then the resolution order. The em-dash clause is functional rather than decorative, carrying the actual behavioral contract.

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 two-optional-parameter resolver with no output schema, the definition covers inputs, resolution behavior, and the shape of the response (confidence + explanation). The remaining gap is minor: it does not say how confidence is expressed or what happens if neither parameter is supplied, though the 'global default → US 4.0 fallback' chain strongly implies that case.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: 'and/or' signals both parameters are independently optional, and the precedence chain tells the agent that institution_id outranks country_code when both are supplied. That priority relationship is not expressed anywhere in the schema.

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?

States a specific verb (resolve) and resource (grading scale) plus the input domain (institution and/or country). The stated resolution chain makes it clearly the aggregator/lookup-of-record rather than a raw listing tool, which distinguishes it from siblings like get_country_grading_systems.

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?

The description gives clear context for use: call it when you need 'the applicable' scale for an institution and/or country, including when only one of the two identifiers is known. It does not explicitly exclude or name the sibling tools to use instead when you want raw country profiles, so it stops short of full when/when-not guidance.

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.