Skip to main content
Glama

IELTSera — IELTS Band Score, CLB & Writing Coach

Get My IELTSera Progress & Today's Study Plan

get_my_ieltsera_progress
Read-onlyIdempotent

Authenticated Tool (Requires IELTSera Personal Access Token): Fetches the connected learner's live IELTSera Band Signal, target band goals, skill-by-skill current estimates (Listening, Reading, Writing, Speaking), weakest rubric criterion, and today's adaptive study plan tasks.

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_my_ieltsera_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered; the description adds the genuinely new fact that a Personal Access Token is required and that the values are 'live'. It also enumerates what the payload contains, which matters because no output schema exists. It stops short of describing behavior when no account is connected or no progress data exists.

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 sentence with the authentication precondition front-loaded and every listed field earning its place. The long comma-separated enumeration of return fields is dense but functional; it could be split into a short purpose line plus a payload line for faster scanning.

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 zero-parameter read tool with no output schema, the description carries the return-value burden well by naming each data component, and it discloses the auth requirement. The remaining gap is failure/empty states (what happens with an invalid or missing token, or a learner with no recorded attempts).

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

Parameters5/5

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

Zero parameters, so the baseline is 4, and the description adds real meaning by clarifying that the learner is implied by the token ('the connected learner's') rather than passed as an identifier. That removes the only ambiguity an agent could have about a parameterless tool.

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 ('Fetches') and a precisely enumerated resource: Band Signal, target goals, four skill estimates, weakest rubric criterion, and today's study plan tasks. None of the siblings (practice prompt, guides, writing analysis, band calculator, pathway, vocabulary) overlap with this per-learner progress read, so an agent can route correctly without opening a 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?

Usage is only implied: the name and the 'connected learner's live' framing make it obvious this is the progress-summary call, but the description never says when to prefer it, nor excludes alternatives such as calculate_ielts_band_score. For a zero-argument read tool with an unambiguous name this is adequate, but explicit routing language 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