Skip to main content
Glama

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

Zalo Send Message

zalo_send_message
Destructive

Sends a Zalo message to a conversation. WRITE operation with a preview gate: the first call (confirm=false) returns a preview WITHOUT sending; set confirm=true to actually send. to is a thread id from zalo_list_chats; set type="group" for a group.

Input Schema

NameRequiredDescriptionDefault
toYesThread id (from zalo_list_chats).
typeNo"user" (default) or "group".
confirmNoMust be true to actually send. Without it, returns a preview.
messageYesText to send.
rememberNoWith confirm: true, also stop asking for this kind of action from now on. Only when the person said so ("don't ask again"). The person can revoke it in LMCP or with set_always_allowed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / remember
      Added value: +{
+  "description": "With confirm: true, also stop asking for this kind of action from now on. Only when the person said so (\"don't ask again\"). The person can revoke it in LMCP or with set_always_allowed.",
+  "type": "boolean"
+}
  2. Added
  3. Removed
  4. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag readOnlyHint=false and destructiveHint=true, but the description adds genuinely new behavioral context: the two-step preview gate means the first call does not send. It does not explain why the tool is destructive (e.g., that a sent message cannot be recalled) or any rate/permission constraints, so it stops short of full transparency.

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?

Three tight sentences, front-loaded with the write/preview-gate mechanic that matters most, then the thread-id and group-type details. No filler.

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 5-parameter mutation tool with no output schema, the description covers the critical mechanics (preview vs send, thread source, group flag) and describes what the first call returns. It omits failure behavior and irreversibility, a minor gap given the rich annotations.

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% and every parameter is already documented in the schema, including the confirm gate and the `remember` permission persistence. The description mostly restates that (to comes from zalo_list_chats, type=group for groups), so it adds little beyond the schema baseline.

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 and resource ('Sends a Zalo message to a conversation') and the platform prefix plus explicit sibling reference (zalo_list_chats) makes it distinguishable from zalo_read_messages, zalo_search_messages, and the other platform senders.

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?

Gives concrete operating instructions: first call with confirm=false returns a preview, set confirm=true to actually send, and get `to` from zalo_list_chats with type="group" for groups. It lacks any explicit 'do not use when...' or cross-platform alternative guidance (e.g., vs whatsapp_send_message), which keeps it from a 5.

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

All Local MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources