Skip to main content
Glama

IELTSera — IELTS Band Score, CLB & Writing Coach

Get IELTS Writing, Speaking & Reading Practice Prompt

get_ielts_practice_prompt
Read-onlyIdempotent

Returns a realistic IELTS practice prompt (Writing Task 2 essay, Academic Task 1 report, General Training Task 1 letter, Speaking Part 1/2/3 cue card, or Reading True/False/Not Given drill) along with a Band 8.0 examiner checklist and a direct deep-link to practice in IELTSera Studio.

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": {
      "taskType": "<taskType>"
    },
    "name": "get_ielts_practice_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskTypeYesWhich IELTS task type to fetch.
topicKeywordNoOptional topic keyword filter (e.g., 'urbanization', 'energy', 'housing', 'automation').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds real value beyond them by disclosing the exact payload an agent will receive – the prompt itself, a Band 8.0 examiner checklist, and a deep-link into IELTSera Studio – which tells the caller what to do with the result. It says nothing about behavior when no prompt matches the topic filter, the only notable gap.

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 whose core ('Returns a realistic IELTS practice prompt') comes first, followed by the supporting enumeration. The long parenthetical of task types is dense but each item earns its place by mapping to an enum value; a bulleted list would read slightly better.

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-parameter read-only fetch with 100% schema coverage, the description supplies the one thing the schema cannot: the shape of the return value and its companion artifacts. It is nearly complete; only fallback behavior for an unmatched topicKeyword is left unstated, and no output schema exists to cover it.

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 the taskType enum is fully documented, so the schema already carries the parameter burden. The description restates the task types in human-readable prose, which aids comprehension but adds no new semantics for taskType or for topicKeyword's filtering behavior on the response.

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 ('Returns') and resource ('a realistic IELTS practice prompt'), then enumerates all seven concrete artifact types (Task 2 essay, Academic Task 1 report, GT Task 1 letter, Speaking Part 1/2/3 cue cards, Reading T/F/NG drill). It also names the two accompanying payloads (Band 8.0 examiner checklist, deep-link), which clearly separates it from siblings like calculate_ielts_band_score or analyze_writing_structure.

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 implied by the enumeration of task types and the mention of practicing in IELTSera Studio, so an agent can infer this is the tool for fetching practice material. However, it never states when to prefer it over search_ieltsera_guides or recommend_ielts_pathway, and gives no exclusions or prerequisites.

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