Skip to main content
Glama

ingilizce.io – English Vocabulary Video Tutor

get_word_lesson

Read-only

Fetch the complete bilingual (Turkish & English) vocabulary video lesson for an English word on ingilizce.io, including CEFR level (A1–C1), Archipelago, Assistant Captain, 3 meanings, example sentences, common collocations, usage note, and clickable YouTube & ingilizce.io lesson URLs.

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": {
      "word": "<word>"
    },
    "name": "get_word_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoReturn Turkish ("tr"), English ("en"), or both ("both") lesson sections.both
wordYesEnglish word to look up (e.g. "abandon", "culture", "ice cream").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description corroborates the open-world nature by naming the external site and clickable YouTube/ingilizce.io URLs. It does not disclose failure behavior for non-existent words, whether access is public or gated, or any rate limits, so it adds only moderate context beyond structured fields.

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 dense sentence that front-loads the verb and resource before listing the payload. The long enumeration is functional rather than padding, though it reads as a run-on and could be split for scannability.

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 no output schema, enumerating the returned fields (CEFR level, meanings, collocations, URLs) is exactly the right compensation and is done thoroughly. The main remaining gap is edge-case behavior for words that have no lesson, which an agent would need to know before calling.

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 both parameters are already documented in the schema, including the tr/en/both enum. The description reinforces the bilingual semantics of the lesson but adds no new detail about the word format (e.g. case sensitivity, multi-word phrases) beyond the schema's examples.

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?

The description uses a specific verb ('Fetch') plus a well-defined resource ('complete bilingual vocabulary video lesson for an English word') and even names the source site, ingilizce.io. It doesn't explicitly contrast itself with siblings like search_vocabulary or build_word_quiz, but the enumerated payload (CEFR level, Archipelago, 3 meanings, collocations, URLs) makes the scope unmistakable.

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: an agent can infer this is the tool for pulling a full lesson on one known English word, versus searching or quizzing. There is no explicit when-to-use statement, no exclusions, and no mention of what to do when the word is unknown or misspelled.

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