Skip to main content
Glama

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

Zalo Connect

zalo_connect
Destructive

Link Zalo to Local MCP by showing a QR code right here in the chat. Call this, then on your phone open Zalo → the QR-scan option, and scan it. After you scan, Zalo tools (zalo_list_chats, zalo_send_message) start working. If Zalo is already linked, it says so. Zalo allows only ONE linked web session at a time — if Zalo Web / another device is open, it may end this one.

Input Schema

NameRequiredDescriptionDefault
confirmNoIgnored; kept for older clients.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to show the QR (it also opens in Preview). Without it the call returns a preview and opens nothing."New value: +"Ignored; kept for older clients."
  2. Changed1 schema field changed
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Must be true to show the QR (it also opens in Preview). Without it the call returns a preview and opens nothing.",
+  "type": "boolean"
+}
  3. Added
  4. Removed
  5. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already mark this non-read-only, open-world, and destructive; the description earns extra credit by explaining WHY it is disruptive — linking may end an existing Zalo Web session — and by disclosing the idempotent "already linked" response. It stops short of stating QR validity windows or failure/timeout behavior, so it is strong but not exhaustive.

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?

Four short sentences, each carrying distinct information: the action, the phone-side steps, the post-conditions, and the one-session caveat. The core action is front-loaded and the risk warning closes the text.

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

Completeness5/5

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

For an auth/connect tool with an output schema present and annotations covering the safety profile, the description supplies everything an agent needs: the interaction flow, the dependency on human QR scanning, the success signal, and the side-effect on other sessions.

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?

The only parameter is the vestigial `confirm` boolean, and the schema already documents it as ignored for older clients at 100% coverage. The description adds nothing about parameters, but there is effectively nothing meaningful to document, so the baseline for a no-op parameter set applies.

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?

States a specific verb and resource: "Link Zalo to Local MCP by showing a QR code." It also names the downstream tools that become usable (zalo_list_chats, zalo_send_message), which distinguishes it from siblings like zalo_disconnect, zalo_diagnose, and the parallel WhatsApp/Telegram connect tools.

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

Usage Guidelines5/5

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

Gives an explicit call sequence (call this, then scan on phone) and a precondition (Zalo tools only start working after scanning). It also covers the already-linked case and warns that only one linked web session is allowed, so an agent knows exactly when to invoke it and what friction to expect.

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