Skip to main content
Glama

IELTSera — IELTS Band Score, CLB & Writing Coach

Save Vocabulary to My IELTSera Flashcards

save_vocabulary_flashcard
Idempotent

Authenticated Tool (Requires IELTSera Personal Access Token): Saves a vocabulary word or collocation from the conversation into the connected learner's IELTSera spaced-repetition flashcard progress and bookmarks it in their Learning Hub.

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": {
      "term": "<term>"
    },
    "name": "save_vocabulary_flashcard"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesThe English word, academic collocation, or card ID to save to the learner's IELTSera vocabulary deck.
contextNoteNoOptional example sentence or usage note discussed during the chat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the write/idempotent/safe profile is known. The description adds real value beyond that: it discloses the authentication requirement (Personal Access Token) and that the write has two distinct effects — updating spaced-repetition progress and bookmarking in the Learning Hub — which an agent could not infer from the annotations alone.

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 that front-loads the authentication requirement and then states the effect and destination. No filler or redundancy; it could be marginally clearer if the auth caveat were separated from the action sentence.

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 two-parameter write tool with annotations covering safety and idempotency and no output schema, the description covers auth, side effects, and destination. Minor gaps remain: it does not clarify that the term may also be a card ID (schema does) or describe what a successful save returns.

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 both parameters are already well documented in the schema, giving a baseline of 3. The description adds only the framing that the term comes 'from the conversation' and does not mention contextNote at all, so it contributes minimal 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?

Names a specific verb ('Saves') and a specific resource ('a vocabulary word or collocation ... into the ... spaced-repetition flashcard progress'), plus a second effect (bookmarking in the Learning Hub). This is unmistakably distinct from every listed sibling, which deal with progress reads, guides, writing analysis, band scores, prompts, and pathways.

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?

The phrase 'from the conversation' implies the intended moment of use (capturing a term discussed in chat), which is useful implied guidance. However, there is no explicit when-not guidance, no statement about what to do if the learner already has the term (beyond the idempotent annotation), and no named alternative tool.

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