Skip to main content
Glama

Ôn từ vựng

on_tu_vung
Read-only

Dùng khi giáo viên hoặc học sinh muốn ôn từ vựng (tiếng Anh, ngoại ngữ khác, thuật ngữ chuyên ngành như y khoa) từ một danh sách từ. Nhận danh sách từ (từ, nghĩa tiếng Việt, tuỳ chọn phiên âm, loại từ, câu ví dụ có chứa từ đó). Mở bộ ôn tập trong widget: thẻ ghi nhớ có đọc phát âm, bài tự luyện tự sinh câu hỏi (chọn nghĩa, chọn từ, gõ từ, điền từ vào câu ví dụ), đua xe chia đội chiếu lên lớp, và chuyển sang Đố vui chia đội hay Ô chữ. Trả kèm link gửi học sinh tự ôn trên điện thoại. Nên có câu ví dụ cho từng từ để có dạng câu điền từ. Opens vocabulary flashcards, self-practice and a team race.

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": {
      "tu": "<tu>"
    },
    "name": "on_tu_vung"
  }
}

Input Schema

NameRequiredDescriptionDefault
tuYesDanh sách từ / words
ten_baiNoTên bài, ví dụ "Unit 3 – My friends" / lesson title
ngon_nguNoNgôn ngữ của widget và câu trả lời: "en" khi người dùng viết tiếng Anh, "vi" khi viết tiếng Việt / UI language: use "en" when the user writes in Englishvi
giong_docNoGiọng đọc phát âm: en-US, en-GB, fr-FR, zh-CN, ja-JP, ko-KR, de-DE, vi-VN hoặc none / voiceen-US

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / ngon_ngu
      Added value: +{
      +  "default": "vi",
      +  "description": "Ngôn ngữ của widget và câu trả lời: \"en\" khi người dùng viết tiếng Anh, \"vi\" khi viết tiếng Việt / UI language: use \"en\" when the user writes in English",
      +  "enum": [
      +    "vi",
      +    "en"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / tu / items / properties / nghia / description
      Previous value: -"Nghĩa tiếng Việt ngắn gọn / meaning"New value: +"Nghĩa ngắn gọn: tiếng Việt, hoặc định nghĩa tiếng Anh đơn giản khi người dùng viết tiếng Anh / short meaning or simple English definition"
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false; the description goes well beyond that by explaining that a review session is opened in a widget, that questions are auto-generated in four formats, that a team race can be projected to the class, and that a shareable link for phone self-study is returned. It does not claim any persistence or destructive effect, so nothing conflicts with readOnlyHint, but it stops short of saying how many words per round or what limits apply to the generated set.

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 trigger condition is front-loaded in the first clause, and the remaining sentences cover inputs, generated modes, and the returned link in a logical order. It is dense but the enumeration of widget modes is slightly padded ("đua xe chia đội chiếu lên lớp" could be tighter), and the trailing English sentence partially duplicates the Vietnamese modality list.

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?

With four parameters, an enum-rich schema, and no output schema, the description carries exactly the load it needs to: it explains what the widget shows, what question types get generated, and that a student share link is returned. Nothing an agent needs in order to call this correctly appears to be missing.

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 every parameter is already documented in the schema, which sets the baseline at 3. The description does add a small amount of meaning by restating the word-object shape and explaining the payoff of vi_du (it unlocks the fill-in-the-blank question type), but it adds no constraint or format guidance for ten_bai, ngon_ngu, or giong_doc.

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?

States a specific verb + resource: it builds and opens a vocabulary review set in a widget from a supplied word list, and enumerates the concrete artefacts (flashcards with pronunciation, auto-generated practice questions, team race, plus a switch to quiz/crossword siblings). An agent can distinguish it from do_vui_chia_doi and o_chu_hang_ngang, which are named as downstream destinations rather than substitutes.

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?

"Dùng khi giáo viên hoặc học sinh muốn ôn từ vựng" gives an explicit actor and trigger condition, and the closing note recommends supplying an example sentence per word so the fill-in-the-blank format becomes available. What is missing is an explicit when-not or a clear statement of when to start directly in Đố vui / Ô chữ instead, so the routing choice remains implied.

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