Skip to main content
Glama

Phản hồi nhanh (sinh viên trả lời bằng điện thoại)

phan_hoi_nhanh
Read-only

Dùng khi giảng viên muốn hỏi cả lớp và xem ngay mức hiểu bài: sinh viên quét mã QR, trả lời bằng điện thoại, kết quả hiện trên màn hình chiếu. Nhận danh sách câu hỏi: trắc nghiệm (2–6 lựa chọn, có hoặc không có đáp án đúng; không có đáp án là câu khảo sát) hoặc trả lời ngắn (có thể ghi nhiều đáp án chấp nhận, ngăn bằng "/"). Rất hợp với câu hỏi tình huống lâm sàng, dược lý, thuật ngữ cho sinh viên khối sức khoẻ. Trả về link mở sẵn câu hỏi; giảng viên bấm "Mở phòng" trên web để có mã QR (phòng cần trình duyệt nên không mở trong khung chat). Opens a live classroom poll / quiz where students answer on their phones.

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

Input Schema

NameRequiredDescriptionDefault
cau_hoiYesDanh sách câu hỏi / questions
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
ten_buoiNoTên buổi học / session title
yeu_cau_ho_tenNoBắt sinh viên nhập họ tên để xuất bảng kết quả theo tên / require student names

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.5/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses a non-obvious two-step flow: the call returns a link with questions pre-loaded, but the instructor must click "Mở phòng" on the web page to obtain the QR code, and the room cannot render inside the chat frame because it requires a browser. That is exactly the kind of operative context an agent needs to set the right expectation and avoid retrying or reporting failure.

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 description is front-loaded with the when-to-use clause, followed by input shape and then the return/instructor-workflow detail, all of which earn their place. Slightly verbose, and the trailing English sentence duplicates the Vietnamese summary, but it is defensible for language coverage.

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?

With no output schema, the description correctly carries the burden of explaining what comes back (a link with questions pre-loaded) and what the instructor must do next. It does not mention the 60-question cap or question-length limits, though those are visible in the schema, so completeness is high but not exhaustive.

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; the description still adds framing by presenting the two question modes as a design choice (multiple choice with 2–6 options, where omitting the correct answer makes it a survey; short answer accepting multiple answers separated by "/"). Much of this restates the schema field descriptions, so it earns above baseline but not a 5.

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?

The description states a specific verb and resource: it opens a live classroom poll where students answer on their phones and results appear on the projector screen. It is instantly distinguishable from siblings such as dem_nguoc or goi_ten_ngau_nhien, and the closing English sentence reinforces the same scope for non-Vietnamese readers.

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ảng viên muốn hỏi cả lớp và xem ngay mức hiểu bài" gives a clear triggering context, and it further narrows suitability to clinical/pharmacology/terminology questions for health-science students. It does not explicitly say when to avoid it or name an alternative sibling, so it stops short of full routing guidance.

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