zalo_send_message
Sends a Zalo message to a conversation, enabling AI agents to communicate via Zalo on your Mac.
Instructions
Sends a Zalo message to a conversation.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Sends a Zalo message to a conversation, enabling AI agents to communicate via Zalo on your Mac.
Sends a Zalo message to a conversation.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations; description only says 'sends' without disclosing behavioral traits such as whether previous connection is required, whether it returns a message ID, or what happens on failure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence is concise but too brief for a tool with no parameters; fails to provide essential context on how inputs are obtained.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Description omits prerequisites (e.g., connection step), message format, and conversation identification method. For a 0-param tool, it lacks completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has zero parameters; description does not explain how the tool knows which conversation or what message content. Baseline for 0 params is 4, but lack of explanation reduces score.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states verb 'Sends', resource 'Zalo message', and target 'conversation'. It distinguishes from sibling messaging tools by specifying Zalo platform.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives like send_message or signal_send_message. No prerequisites mentioned (e.g., need to connect to Zalo first).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lanchuske/local-mcp-releases'
If you have feedback or need assistance with the MCP directory API, please join our Discord server