Skip to main content
Glama

Ô chữ hàng ngang

o_chu_hang_ngang
Read-only

Dùng khi giáo viên muốn tổ chức trò chơi ô chữ (giải ô chữ hàng ngang, tìm từ khoá hàng dọc) để khởi động hoặc ôn bài trên lớp. Nhận các hàng ngang (câu gợi ý + đáp án) và từ khoá hàng dọc tuỳ chọn; hàng thứ i phải chứa chữ cái thứ i của từ khoá (so sánh sau khi bỏ dấu, viết hoa). Đáp án nên ngắn (1–3 từ, tối đa 20 chữ cái). Mở ô chữ trong widget: chọn hàng, đồng hồ, mở đáp án, đoán từ khoá, cộng điểm theo đội; trả kèm link chơi toàn màn hình trên web. Opens a classroom crossword game with a vertical keyword.

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": {
      "hang_ngang": "<hang_ngang>"
    },
    "name": "o_chu_hang_ngang"
  }
}

Input Schema

NameRequiredDescriptionDefault
giayNoSố giây cho mỗi hàng, 0 là không bấm giờ / seconds per row
so_doiNoSố đội tính điểm (2–6), 0 là không chia đội / number of teams
ten_doiNoTên các đội / team names
tu_khoaNoTừ khoá hàng dọc; số chữ cái (sau khi bỏ dấu, bỏ khoảng trắng) phải bằng số hàng ngang / vertical keyword
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
hang_ngangYesCác hàng ngang theo thứ tự / rows
goi_y_tu_khoaNoCâu gợi ý cho từ khoá / keyword clue

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. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only say readOnly and closed-world; the description adds real behavior: it opens an in-widget crossword with row selection, timer, answer reveal, keyword guessing and team scoring, and returns a fullscreen web play link. It also discloses the hard structural constraint (row i must contain the i-th letter of the keyword, compared after stripping diacritics and uppercasing) and answer-length advice.

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 when-to-use sentence, then inputs and constraints, then widget behavior and return value — a logical order with no wasted preamble. The closing English sentence "Opens a classroom crossword game with a vertical keyword" largely restates the opening and is the one redundant element.

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 tool with no output schema, the description does supply the return value (fullscreen play link) and the in-widget interaction model, plus the key content constraint on keyword/row alignment. Remaining details such as scoring mechanics or what so_doi=0 produces are left to the schema, which is acceptable but leaves the picture slightly thin.

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 coverage is 100%, so the schema already documents all seven parameters, establishing a baseline of 3. The description adds a cross-parameter rule not expressible in the schema (keyword letter count must equal row count, with letter alignment per row) and answer-length guidance, but it does not touch timer, team count, or language parameters.

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?

Names a specific verb and resource: organizing a horizontal-row crossword game with a vertical keyword, including the exact inputs (rows of clue+answer, optional keyword). The game type is distinctive enough that an agent can separate it from siblings like on_tu_vung or do_vui_chia_doi, 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?

"Dùng khi giáo viên muốn tổ chức trò chơi ô chữ ... để khởi động hoặc ôn bài trên lớp" gives a clear usage context (warm-up or review). There is no explicit when-not guidance or named alternative tool for a plain vocabulary review, 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