Skip to main content
Glama

Đố vui chia đội

do_vui_chia_doi
Read-only

Dùng khi giáo viên muốn tổ chức trò chơi đố vui, ôn tập hay kiểm tra nhanh theo đội trên lớp. Nhận bộ câu hỏi (trắc nghiệm hoặc tự luận) và mở trò chơi: chiếu từng câu kèm đồng hồ, hiện đáp án, cộng điểm cho đội trả lời đúng, cuối cùng hiện bảng xếp hạng. Trả kèm link mở trò chơi trên web để chiếu toàn màn hình. Opens a team quiz game for classroom review from the given questions.

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": {
      "cau_hoi": "<cau_hoi>"
    },
    "name": "do_vui_chia_doi"
  }
}

Input Schema

NameRequiredDescriptionDefault
giayNoSố giây cho mỗi câu, 0 là không bấm giờ / seconds per question
so_doiNoSố đội / number of teams
cau_hoiYesDanh sách câu hỏi / questions
ten_doiNoTên các đội, ví dụ Tổ 1, Tổ 2; bỏ trống để dùng tên màu / team names
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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"
      +}
  2. 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=true and openWorldHint=false, and the description adds real value on top: the full runtime sequence of the game and the fact that a web link is returned for fullscreen projection. 'Opens a game' and 'cộng điểm' could momentarily read as state mutation against readOnlyHint, but the scoring is clearly in the generated widget, so this is mild tension rather than a contradiction.

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?

Front-loaded with the trigger, then the gameplay flow, then the return value — a sensible order with no filler. The closing English sentence largely restates the opening Vietnamese sentence, a small redundancy that keeps it from a 5.

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 5-parameter tool with a nested question array and no output schema, the description covers trigger, behavior and return value (a web link), which is what an agent needs to select and call it. Edge-case behavior (invalid questions, whether a session persists) is unspecified but not essential for invocation.

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% and each parameter already carries bilingual documentation, so the baseline is 3. The description only implies the question payload (multiple-choice or open-ended) and says nothing about giay, so_doi, ten_doi or ngon_ngu beyond what the schema states.

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 and resource: organize a team quiz game from a supplied question set, with the gameplay flow spelled out (per-question timer, answer reveal, scoring, final leaderboard). The phrase 'theo đội' and the question-set input distinguish it from siblings like o_chu_hang_ngang or chia_nhom_ngau_nhien, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit trigger: 'Dùng khi giáo viên muốn tổ chức trò chơi đố vui, ôn tập hay kiểm tra nhanh theo đội trên lớp', which tells the agent both the audience and the classroom-review context. It gives no when-not conditions and does not route to alternatives, so it stops short of a 5.

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