Joe Speaking

IELTS topic coverage and practice gaps

get_question_bank_progress

Read-onlyIdempotent

Returns the signed-in learner's cloud-synced IELTS question-bank coverage and per-topic attempts, best score, last-practised time and needs-work status. Recording Practice question items, Live Conversation topic groups and combined topic-group coverage are separate; coverage is a 0–1 fraction and needs-work means best score below 6. Bank coverage is exam- and bank-scoped, not lifetime history or CELPIP task progress. Read-only. Use when the learner wants to find unpractised IELTS topics, revisit weak topics, or compare coverage before choosing the next question. Speaking practice, recording, scoring and mock tests take place in Joe Speaking. The legacy top-level coverage is combined topic-group coverage, distinct from Recording Practice question-item progress. Zero bank coverage is not lifetime history.

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

Input Schema

Name	Required	Description
`limit`	No	Maximum topics per page, from 1 to 50; defaults to 50.
`cursor`	No	Opaque continuation for the topic list.
`market`	No	Regional bank to report against, when the season has one.
`seasonId`	No	Question-bank season. Defaults to the current practice season.
`includeTopics`	No	Whether the result includes the per-topic breakdown.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026

changedInput schema / properties / includeTopics / description

Previous value: -"Include the per-topic breakdown."New value: +"Whether the result includes the per-topic breakdown."

First observedOct 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, and the description adds real substance on top: coverage is a 0-1 fraction, needs-work means best score below 6, coverage is bank- and exam-scoped rather than lifetime history, and zero coverage is explicitly not lifetime history. The only wasted clause is the restated 'Read-only.', which duplicates readOnlyHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded, but the middle section repeats itself: the separation of Recording Practice question items and combined topic-group coverage is stated twice, and 'not lifetime history / zero bank coverage is not lifetime history' appears in two forms. Roughly a third of the text is restatement rather than new information.

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 no output schema and five optional parameters, the description does the needed work by explaining what the returned coverage figures mean (0-1 fraction, needs-work threshold) and what scope they reflect. Only the relationship between the legacy top-level coverage figure and the includeTopics breakdown stays slightly murky.

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%, with limit, cursor, market, seasonId and includeTopics all documented in the schema, so the schema carries the parameter burden. The description adds no per-parameter meaning such as when to set includeTopics or how market interacts with seasonId; baseline 3 applies.

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 first sentence names the exact resource (the signed-in learner's cloud-synced IELTS question-bank coverage) and enumerates the returned fields: per-topic attempts, best score, last-practised time and needs-work status. It then explicitly separates itself from Recording Practice question items, Live Conversation topic groups and CELPIP task progress, so an agent can distinguish it from siblings without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives three concrete triggering situations (find unpractised IELTS topics, revisit weak topics, compare coverage before choosing the next question) and states where related work happens instead (Joe Speaking for speaking practice, recording, scoring and mock tests). The bank-scoped-not-lifetime distinction further tells the agent when this tool would return misleading results.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Joe Speaking tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?