Skip to main content
Glama

Vòng quay may mắn

vong_quay_may_man
Read-only

Mở vòng quay may mắn tương tác: vòng quay nhiều màu, kim chỉ, tiếng tích tắc, pháo giấy khi có kết quả. Người dùng tự bấm Quay (hoặc vuốt vòng), mỗi lượt chọn 1 đến 5 ô, có thể bỏ ô đã trúng. Dùng cho: vòng quay may mắn, quay thưởng, rút thăm trúng thưởng, bốc thăm phần thưởng, câu hỏi, chủ đề, thứ tự tổ, hoặc quay tên học sinh. Không truyền danh_sach thì dùng mẫu phần thưởng cho lớp. Opens an interactive spin wheel (prize wheel, random draw, wheel of names, random picker) with sound and confetti; the user spins it. Items can be names, prizes, questions or topics.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vong_quay_may_man"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
danh_sachNoCác ô trên vòng quay: tên học sinh, phần thưởng, câu hỏi, chủ đề… mỗi phần tử một ô. Bỏ trống để dùng mẫu phần thưởng. Wheel items, one per element; omit for sample rewards.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond readOnlyHint=true and openWorldHint=false, the description discloses meaningful behavior: the wheel is interactive and spun by the user (not the model), each spin yields 1–5 cells, already-won cells can be removed, and sound/confetti fire on results. It does not say whether the outcome is returned to the caller, which matters since there is no output schema — that gap keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded, but the entry duplicates itself across Vietnamese and English paragraphs with largely overlapping content. The English sentence does add useful synonym coverage ('wheel of names, random picker') that aids matching, yet the overall length is inflated for two optional parameters.

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-optional-parameter widget with no output schema and already-declaring annotations, the entry covers what is created, who drives it, default data, and typical use cases — enough to call it correctly. The remaining ambiguity is whether the spin result comes back to the agent versus living only in the UI.

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 both parameters are documented with examples, so the schema does the heavy lifting. The description only restates the danh_sach default ('Không truyền danh_sach thì dùng mẫu phần thưởng cho lớp'), adds item-type examples that the schema already lists, and says nothing about the ngon_ngu language switch or the 200-item cap. Baseline 3 applies.

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: 'Mở vòng quay may mắn tương tác' / 'Opens an interactive spin wheel', with concrete visual/audio traits (many-colored wheel, needle, ticking, confetti) that make it identifiable. It never distinguishes itself from plausible siblings such as goi_ten_ngau_nhien (random name calling) or chia_nhom_ngau_nhien, even though 'quay tên học sinh' clearly overlaps with them, so differentiation is left to inference.

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?

Explicitly enumerates when to use it: prize wheel, lucky draw, raffle, reward draw, questions, topics, group ordering, or spinning student names, plus the default behavior when danh_sach is omitted. There is no when-not-to-use guidance and no mention of the random-selection siblings it overlaps with, which keeps it below 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