Skip to main content
Glama

IELTSera — IELTS Band Score, CLB & Writing Coach

Calculate IELTS Band Score & Canadian CLB

calculate_ielts_band_score
Read-onlyIdempotent

Calculates official IELTS Overall Band scores (with 0.25/0.75 half-band rounding rules), converts Listening and Academic/General Training Reading raw scores (0-40) into Band scores, computes weighted Writing Band (1/3 Task 1 + 2/3 Task 2), and maps scores to Canadian Language Benchmarks (CLB 4-10) for Express Entry.

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

Input Schema

NameRequiredDescriptionDefault
examTrackNoIELTS exam module ('academic' or 'general_training'). Defaults to 'academic'.
readingBandNoReading band score (0 to 9 in 0.5 increments). Optional if readingRawCorrect is provided.
writingBandNoWriting band score (0 to 9 in 0.5 increments). Optional if writingTask1Band and writingTask2Band are provided.
speakingBandNoSpeaking band score (0 to 9 in 0.5 increments).
listeningBandNoListening band score (0 to 9 in 0.5 increments). Optional if listeningRawCorrect is provided.
writingTask1BandNoWriting Task 1 band score (weighted 1/3 of total Writing score).
writingTask2BandNoWriting Task 2 band score (weighted 2/3 of total Writing score).
readingRawCorrectNoNumber of correct Reading answers out of 40 (0-40). Uses official Academic vs GT conversion tables.
listeningRawCorrectNoNumber of correct Listening answers out of 40 (0-40).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuine domain behavior beyond them: the 0.25/0.75 half-band rounding convention, the 1/3 + 2/3 Writing weighting, official Academic vs GT conversion tables, and the CLB 4-10 range. It stops short of saying what happens when inputs are missing or contradictory (e.g., both readingBand and readingRawCorrect supplied).

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 with no filler; every clause maps to a real capability. It is dense enough that splitting the scoring rules from the CLB mapping would aid scanning, but nothing is redundant.

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 9-parameter, all-optional pure-computation tool with no output schema, the description does convey the returned artifacts (band scores plus CLB) and the standards used. The remaining gap is behavior on incomplete or conflicting inputs, which matters more here precisely because every parameter is optional.

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, and the description earns one above it by stating the rounding rule and weighting formula that the schema never expresses, plus the CLB 4-10 output range. It still does not clarify precedence when an optional band and its raw-score alternative are both provided.

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 names a precise verb ('Calculates') and enumerates the exact resources computed: Overall Band with half-band rounding, raw-to-band Listening/Reading conversion, weighted Writing Band, and CLB mapping. None of the siblings (practice prompts, pathway recommendations, writing analysis) do scoring arithmetic, so an agent can route here without inspecting another schema.

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 description implies the use case (score conversion and CLB lookup for Express Entry), but never states when to prefer this over a sibling or what minimum input set is needed. With zero required parameters, guidance on 'provide at least a band or a raw score' is exactly what an agent would need and it is absent.

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.

Resources