Skip to main content
Glama

IELTSera — IELTS Band Score, CLB & Writing Coach

Search IELTSera Strategy Guides

search_ieltsera_guides
Read-onlyIdempotent

Searches IELTSera's 40 expert IELTS strategy guides and examiner playbooks for specific questions, question types, Band 6.0 vs Band 8.0 comparisons, comparison tables, and actionable fixes.

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": {
      "query": "<query>"
    },
    "name": "search_ieltsera_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of matching guides to return (1 to 5, default 3).
queryYesSearch query or IELTS topic (e.g. 'True False Not Given', 'Academic Task 1 overview', 'CLB 9', 'One Skill Retake', 'Speaking Part 2 cue card', 'Band 7 writing').
categoryNoOptional category filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world corpus, so the safety profile is covered. The description adds useful bounded scope (exactly 40 guides, examiner playbooks) but says nothing about result format, snippet length, or match behavior for the query.

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?

A single dense sentence with zero filler, front-loaded with the verb and resource before the content enumeration. Nothing in it could be removed without losing routing 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?

For a simple, read-only, fully-described 3-parameter search tool this is essentially complete: corpus size, covered content, and filters are all clear. The only minor gap is that with no output schema, nothing indicates what a returned result looks like.

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%, so query examples, the 1-5 limit default, and the category enum are all documented in structured fields. The description's mention of question types and comparison tables loosely maps to the query parameter but adds no syntax or semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Searches) and a well-scoped resource (IELTSera's 40 expert IELTS strategy guides and examiner playbooks), then enumerates the content types it covers (question types, Band comparisons, comparison tables, fixes). The resource and content scope are distinct enough from siblings like analyze_writing_structure or get_ielts_practice_prompt that an agent can route correctly, though no sibling is named explicitly.

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 content enumeration: use it for strategy/topic questions, comparisons, and 'how do I fix X' questions. There is no explicit when-not-to-use statement and no named alternative for related tasks such as scoring or practice prompts, so the agent must infer the boundary.

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