Skip to main content
Glama

ingilizce.io – English Vocabulary Video Tutor

get_level_words

Read-only

Retrieve published English vocabulary words and video links for a specific CEFR level (A1, A2, B1, B2, or C1) on ingilizce.io.

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": {
      "level": "<level>"
    },
    "name": "get_level_words"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYesCEFR level to fetch.
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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, so safety is covered. The description adds useful non-annotated context: only 'published' words are returned and results include video links (valuable since there is no output schema), but it never mentions paging behavior for limit/offset.

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 front-loaded sentence with no filler; the resource and scope come first. It is efficient but on the sparse side for a three-parameter list tool.

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

Completeness3/5

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

The read-only, non-destructive nature and the record contents are adequately conveyed for a simple list tool. However, with two undocumented pagination parameters and no output schema, the definition leaves the agent guessing about result volume and paging.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% — limit and offset are undocumented in both schema and description. The description merely repeats the level enum values already in the schema and adds no meaning about defaults, maximums, ordering, or how pagination interacts with the level list.

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?

Specific verb ('Retrieve') plus concrete resources ('English vocabulary words and video links') and a precise scope (a specific CEFR level on ingilizce.io). It does not name or differentiate from siblings like search_vocabulary, which likely overlaps, so it stops short of a 5.

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: an agent with a known CEFR level who wants the level's word list. There is no explicit 'use this instead of X' guidance and no exclusions or prerequisites, leaving the boundary with search_vocabulary to inference.

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