Skip to main content
Glama

Thiệp chúc mừng

thiep_chuc_mung
Read-only

Dùng khi giáo viên muốn tạo, mở hoặc chiếu thiệp chúc mừng cho học sinh, thầy cô hoặc cả lớp. Hiện thiệp có tên, lời chúc, pháo giấy và nhạc YouTube, kèm link thiệp để gửi qua Zalo. Dịp: sinh-nhat (Sinh nhật), 20-11 (Ngày Nhà giáo 20/11), 8-3 (Quốc tế Phụ nữ 8/3), tet (Năm mới, Tết), khen-thuong (Khen thưởng, thành tích), chao-mung (Chào mừng bạn mới). Thiệp sinh nhật mặc định phát "Khúc hát mừng sinh nhật" của Phan Đinh Tùng. Opens a classroom greeting card (birthday, Teachers' Day, Women's Day, New Year, awards, welcome) with an optional YouTube song.

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

Input Schema

NameRequiredDescriptionDefault
dipNoDịp chúc mừng / occasionsinh-nhat
tenNoTên người được chúc; bỏ trống nếu chúc cả lớp / recipient name
bai_hatNoLink YouTube của bài hát muốn phát thay bài mặc định, hoặc "khong" để không phát nhạc / YouTube link or "khong" for no music
loi_chucNoLời chúc riêng; bỏ trống để dùng lời chúc mẫu của dịp / custom message

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 context beyond them: what the card renders (tên, lời chúc, pháo giấy, nhạc YouTube), the Zalo share link, and the default birthday song. The verb "tạo" sits slightly in tension with readOnlyHint, but since the card is rendered client-side rather than persisted, this reads as generation-not-mutation rather than a contradiction. No mention of persistence or whether a created card is saved.

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 trigger condition and occasion list are front-loaded, and every Vietnamese sentence carries information. The trailing English sentence largely restates what precedes it, which is the one piece of avoidable redundancy.

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 4-param, all-optional, read-only display tool with no output schema, the definition covers trigger, occasion vocabulary, defaults, and the resulting shareable link. A brief note on what the tool returns (rendered card vs. link only) would close the last gap.

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 earns extra by glossing each occasion value in human-readable Vietnamese (sinh-nhat = Sinh nhật, 20-11 = Ngày Nhà giáo, etc.) and by disclosing the default music behavior for sinh-nhat, which the schema does not state. It does not add anything about "ten" or "loi_chuc" beyond the schema.

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?

Names a specific verb set (tạo, mở, chiếu) and a specific resource (thiệp chúc mừng) plus the audience (học sinh, thầy cô, cả lớp). None of the siblings (chia_nhom_ngau_nhien, dem_nguoc, do_vui_chia_doi, goi_ten_ngau_nhien, mo_vuong_quoc_lop_hoc) overlap with greeting cards, so the agent can route cleanly.

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ạo, mở hoặc chiếu thiệp..." gives a clear trigger condition and actor. It does not name when NOT to use it or point to any alternative, but the sibling set makes the boundary obvious.

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