Skip to main content
Glama
Sign In
monacloud-mcp

monacloud-mcp

Official
by themonagroup
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Nối nhóm Zalo

monapay_create_zalo_group

Create a Zalo group to receive MONA Pay transaction alerts. Connect a group_id from MONA Account/PMS, choose events, and set a plain-text message template for direct notifications.

Instructions

Nối nhóm có bot Gấu Mona bằng group_id 10–25 chữ số lấy từ MONA Account/PMS; Zalo không parse Markdown, nên template phải là text thuần.

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": {
      "group_id": "<group_id>",
      "friendly_name": "<friendly_name>"
    },
    "name": "monapay_create_zalo_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventsNoCác sự kiện gửi vào nhóm Zalo
group_idYesgroup_id gồm 10–25 chữ số, lấy từ MONA Account/PMS
is_activeNo
friendly_nameYesTên dễ nhớ của nhóm
message_templateNoText thuần; hỗ trợ {amount}, {description}, {virtual_account_number}, {transaction_code}, {transfer_date} và dạng {{...}}
virtual_account_idNoChỉ nhận thông báo cho VA này; bỏ trống = mọi tài khoản

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral transparency burden. It does disclose a non-obvious platform behavior (Zalo ignores Markdown, so templates must be plain text) and clarifies that the group already contains the bot. However, it omits side effects, idempotency, duplicate-connection behavior, permissions, and success/failure response details for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two compact sentences with no filler. It front-loads the primary action and ID constraint, then adds the important template caveat, making every sentence earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers essential ID sourcing and the Markdown constraint, but for a connection operation with no output schema and no annotations, it lacks information about what happens on success or failure, whether reconnecting an already-connected group errors or is idempotent, and how events and is_active interact. The sibling update/delete/test tools are not referenced for follow-up actions.

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?

The input schema already covers 83% of parameters, including group_id source and message_template plain-text requirements, so the description mostly restates schema content. The only added semantic context is the rationale that Zalo does not parse Markdown. This meets the baseline but does not compensate for the undocumented is_active parameter.

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 uses a specific action verb 'Nối' (connect/link) and identifies the resource: a Zalo group containing the Mona bear bot, identified by a 10–25 digit group_id. The action is clearly distinct from sibling list/update/delete/test operations, and the title reinforces that this is about connecting, not creating, a Zalo group.

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?

The description gives clear, actionable context: obtain group_id from MONA Account/PMS and keep message templates as plain text because Zalo does not parse Markdown. It does not explicitly contrast with monapay_update_zalo_group or state when not to use it, so there is room for a 5, but the prerequisites and constraints are clear enough for correct usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools