Skip to main content
Glama

IELTSera — IELTS Band Score, CLB & Writing Coach

Analyze IELTS Writing Structure & Register

analyze_writing_structure
Read-onlyIdempotent

Runs a deterministic IELTS Writing structural, lexical, and register diagnostic on a learner's draft response (Task 2 Essay, Academic Task 1 Report, or General Training Task 1 Letter). Checks word count penalties, paragraph balance, Task 1 Overview presence, GT salutation/sign-off pairing, contraction violations, overused mechanical linkers, and lexical variety.

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>",
      "draftText": "<draftText>"
    },
    "name": "analyze_writing_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskTypeYesThe IELTS Writing task type being analyzed.
draftTextYesThe learner's full draft essay, report, or letter text.
letterToneNoOptional target tone when taskType is 'gt_task_1' (defaults to 'formal').

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, openWorldHint=false and destructiveHint=false, so safety is covered; the description adds the genuinely new trait that the analysis is 'deterministic,' meaning repeat calls yield identical results with no model variance. It does not disclose the shape of the diagnostic output (flags vs. findings vs. counts), which matters since there is no output schema.

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

Conciseness5/5

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

Two sentences, zero filler: the first states the action, target and task coverage; the second lists the specific rule checks. The dense check list is informative rather than padding, and the key scope statement is front-loaded.

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 annotations covering safety and no output schema, the description should still hint at what the diagnostic returns; it lists the checks performed, which partly implies the findings, but does not say whether results are pass/fail flags, counts, or prose. Otherwise the definition is complete enough for correct invocation.

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 coverage is 100% with two enums, so the schema already documents taskType, draftText and letterTone fully. The description corroborates the task-type scope and gestures at register/salutation concerns relevant to letterTone, but adds no format, length, or default behavior details beyond the schema. 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 description opens with a specific verb and resource: 'Runs a deterministic IELTS Writing structural, lexical, and register diagnostic on a learner's draft response,' then enumerates the three task shapes and the concrete checks. An agent can tell this is a static rule-based analysis pass, not a band-score calculator, which cleanly separates it from siblings 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 Guidelines4/5

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

It makes the input context unambiguous — a learner's draft, and which of the three task types it applies to — so an agent knows when the tool fits. It stops short of naming an alternative (e.g., 'use calculate_ielts_band_score for numeric scoring instead') or stating exclusions such as non-IELTS text.

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