Skip to main content
Glama

IELTSera — IELTS Band Score, CLB & Writing Coach

Recommend IELTS Exam & UKVI Pathway

recommend_ielts_pathway
Read-onlyIdempotent

Recommends the exact IELTS exam version (IELTS Academic, IELTS General Training, IELTS for UKVI SELT, or IELTS Life Skills A1/A2/B1), required band thresholds, and preparation roadmap based on the candidate's target country and visa/study goal.

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": {
      "goal": "<goal>",
      "destinationCountry": "<destinationCountry>"
    },
    "name": "recommend_ielts_pathway"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesThe candidate's primary objective.
currentOverallBandNoOptional current estimated overall IELTS band score (0-9).
destinationCountryYesTarget country for study, work, or migration.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the output is conditioned on target country plus visa/study goal, but it says nothing about limitations (e.g., not authoritative for visa eligibility) or how deterministic the recommendation is.

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; the parenthetical enumeration of exam versions earns its space. It is somewhat dense and could be split into purpose plus output summary for faster 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?

With only three parameters, two required, and no output schema, the description usefully enumerates what comes back (exam version, band thresholds, roadmap). The only gap is the unaddressed optional 'currentOverallBand' parameter and any caveat about the advisory nature of the recommendation.

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 description coverage is 100% and both enums are self-documenting, so the baseline applies. The description restates the role of 'destinationCountry' and 'goal' but never mentions 'currentOverallBand' or how an optional current band changes the roadmap, adding little beyond 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 ('Recommends') and an enumerated set of outputs: exam version (Academic, General Training, UKVI SELT, Life Skills A1/A2/B1), band thresholds, and a preparation roadmap. This makes it unmistakably a recommendation/decision tool rather than a scoring tool like calculate_ielts_band_score.

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?

Usage is only implied: the required 'goal' and 'destinationCountry' inputs signal that the tool is for candidates deciding which exam to take. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as calculate_ielts_band_score for candidates who only need a score estimate.

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