Skip to main content
Glama

Vương Quốc Lớp Học

mo_vuong_quoc_lop_hoc
Read-only

Trả về đường dẫn tới Vương Quốc Lớp Học: app quản lý lớp, cộng điểm, thăng cấp và đổi quà cho học sinh. App lưu dữ liệu trên trình duyệt của giáo viên nên phải mở trên web, không chạy trong khung chat. Returns the link to the classroom management game.

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

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • 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. First observed

TDQS

A3.7/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, so the read-only nature is covered. The description adds genuinely non-obvious behavior: the app persists data in the teacher's browser, must be opened in a real web context, and will not function inside the chat iframe — exactly the deployment caveat an agent needs before presenting the link.

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 purpose, then the app's function, then the browser constraint, then a one-line English restatement. The bilingual duplication is a small redundancy, but each sentence serves a distinct purpose 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?

With no output schema, the description correctly states what is returned (a link) and where it must be opened, which is the critical information for this tool. Only minor gaps remain, such as whether the link is stable or session-scoped.

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 the single ngon_ngu parameter is fully documented in-schema with its enum and default, so the schema carries the load. The description adds no parameter meaning at all, but the baseline of 3 applies when the schema is this complete.

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?

The description names a specific verb and resource ("Trả về đường dẫn tới Vương Quốc Lớp Học") and immediately explains what the app is: a classroom management game for scoring points, leveling up, and redeeming rewards. That is enough to tell it apart from siblings like chia_nhom_ngau_nhien or dem_nguoc, though it never explicitly contrasts itself with them.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the tool to call when a teacher wants the classroom game, and the note that it must be opened on the web and cannot run in a chat frame is a real operational constraint. However, there is no explicit when-to-use/when-not guidance and no named alternative for other classroom needs.

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