Skip to main content
Glama

Mark an essay like an IELTS Writing Task 2 examiner (20 credits or $0.100)

mark_ielts_essay
Read-onlyIdempotent

Paste a student essay (60+ words; add the question as prompt). Returns the overall band and the four criterion bands (Task Response, Coherence and Cohesion, Lexical Resource, Grammar) with evidence and one fix each, 3-8 real errors quoted from the essay with corrections, one body paragraph rewritten at band 8, three practice tasks and measured statistics. Feedback language selectable (lang=zh, es, vi, ar, hi, ...). PAID: 20 Iris Credits with a credits key (Authorization: Bearer iris_... header or the key argument; packs from $0.25, buyable with a plain USDC transfer, see payment_options), or $0.100 per call with x402 over MCP (USDC on Base) or MPP over MCP (USDC.e on Tempo). An unpaid call returns the payment terms and charges nothing; bad input is rejected first; failed work is never charged (credits are refunded). Same result as GET /v1/writing/assess.

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": {
      "essay": "<essay>"
    },
    "name": "mark_ielts_essay"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoOptional Iris Credits key (iris_ + 48 hex). Better: set it once as the MCP header Authorization: Bearer <key>. Without a key the call is paid with x402 / MPP over MCP.
langNoLanguage of the feedback comments (quotes, fixes and the rewrite stay in English). Default en.
essayYesThe essay text, 60+ words, max 4500 characters (POST JSON {"essay": ...} also works). Omit for a demo on the built-in sample essay.
promptNoThe Task 2 question the essay answers (improves Task Response judging). Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already establish that this is read-only, idempotent, non-destructive, and open-world. The description adds substantial beyond-schema behavior: paid access via credits or x402/MPP, unpaid calls returning payment terms without charge, bad input being rejected before billing, and failed work being refunded.

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?

The description is front-loaded with purpose and return contents, followed by payment and failure behavior. It is dense and somewhat long because payment rails are complex, but most sentences carry useful invocation or billing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of explaining the return contents, and it does so thoroughly: overall band, four criterion bands, evidence, fixes, quoted errors, rewrite, practice tasks, and statistics. Combined with the fully documented input schema and payment behavior, an agent has enough context to select and invoke it correctly.

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%, so the input schema already documents essay, prompt, lang, and key in detail. The description reinforces that the essay should be 60+ words, the prompt improves Task Response judging, and lang selects feedback language, but it adds little meaning 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?

The description clearly states a specific action and resource: it marks an IELTS Writing Task 2 student essay using examiner-style criteria. It also distinguishes the output from related tools by naming the bands, error quotations, rewrite, practice tasks, and statistics returned.

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 gives clear invocation context: paste the essay, ensure it is 60+ words, and optionally add the Task 2 question as a prompt to improve Task Response judging. It does not explicitly compare this tool with siblings such as essay_statistics or check_text_level, but the usage conditions are otherwise clear.

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