Skip to main content
Glama

Ô số bí mật

o_so_bi_mat
Read-only

Dùng khi giáo viên muốn trò chơi chọn ô số chia đội (kiểu Baamboozle) để khởi động hay ôn bài: câu hỏi giấu sau các ô đánh số, các đội lần lượt chọn ô, trả lời đúng được điểm của ô (điểm bí mật 1–3 lần điểm gốc), xen ô may mắn (quà, bom, cướp điểm, đổi điểm, thêm lượt). Học sinh không cần thiết bị. Khác do_vui_chia_doi (câu hỏi lần lượt, mọi đội cùng trả lời). Trả kèm link mở trò chơi trên web để chiếu toàn màn hình. Opens a Baamboozle-style mystery tile game: teams take turns picking numbered tiles hiding questions, with mystery points and lucky tiles.

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": "o_so_bi_mat"
  }
}

Input Schema

NameRequiredDescriptionDefault
diemNoĐiểm gốc mỗi câu đúng / base points per correct answer
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
o_may_manNoXen ô may mắn không có câu hỏi: quà, bom, cướp điểm, đổi điểm, thêm lượt / include lucky tiles
diem_bi_matNoMỗi ô được 1, 2 hoặc 3 lần điểm gốc, mở ra mới biết / mystery points per tile

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/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 is consistent with a safe generator. Beyond that it adds real context the annotations cannot: the output includes a web link to open the game for full-screen projection, and students need no devices. It stops short of describing how the link is scoped or whether games persist, which is the remaining gap.

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 use case, then the mechanic, then the contrast with the sibling, then the return value. The Vietnamese and English versions duplicate each other, which is slightly redundant, but each Vietnamese sentence carries distinct information and nothing is padded.

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 an 8-parameter tool with no output schema, the description covers what the tool produces (a playable web link), the audience (teacher projecting, students without devices), and the sibling boundary. It does not cover limits like maximum questions or the language parameter's effect, though the schema already documents those bounds.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds gameplay meaning on top: it explains that diem_bi_mat makes each tile worth 1-3x the base score revealed only on open, and that o_may_man injects specific tile types (gift, bomb, steal points, swap points, extra turn). That elaborates the terse 'include lucky tiles' schema line rather than restating it.

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 concrete verb+resource: an interactive Baamboozle-style game where teams take turns picking numbered tiles hiding questions. It also names the distinguishing mechanic (secret 1-3x points, lucky tiles) and explicitly contrasts with the sibling do_vui_chia_doi, so an agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit trigger ('Dùng khi giáo viên muốn trò chơi chọn ô số chia đội ... để khởi động hay ôn bài') and an explicit alternative with the condition that selects it: do_vui_chia_doi is for sequential questions where all teams answer together. The exclusion is stated, not inferred.

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