Skip to main content
Glama

Zalo Business Reference (ZBS Template Message, OA)

Zalo OA plan comparison

oa_plan_compare
Read-onlyIdempotent

Compare the Zalo Official Account plans in force from 1 June 2026 (Cơ bản, Tiêu chuẩn, Tăng trưởng, Toàn diện) with prices including 10% VAT, staff accounts, Open API and its requests-per-minute limit, consultation messages outside the 48-hour window and features, and pick the smallest plan that meets your needs (needs_api, api_requests_per_minute, replies_outside_48h_per_month, staff, features, term_months 6 or 12), with the reason and the paid-reply overage. The Cơ bản price is not published by Zalo. Reference only. Examples: {}; {"needs_api":true,"staff":8}; {"replies_outside_48h_per_month":3000,"features":["chatbot"],"term_months":6}.

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

Input Schema

NameRequiredDescriptionDefault
staffNoStaff accounts that will work in the OA. Default 1.
featuresNoRequired features: chat_basic, chat_advanced_labels_assign_notes, group_chat_gmf, voice_call_basic, voice_call_advanced, mobile_chat_tool, basic_automation, chat_menu, chatbot, extensions, articles_comments_campaign_tool, advanced_reports_activity_log_crm, search_in_zalo_share_qr, follow_invitations, custom_url_priority_features_priority_support.
needs_apiNoThe OA needs the Open API (for integrations or sending template messages through the API). Default false.
term_monthsNoPlan term: 12 (default) or 6 months (6 months only for Tăng trưởng and Toàn diện).
api_requests_per_minuteNoPeak OA API requests per minute (implies needs_api when above 0).
replies_outside_48h_per_monthNoConsultation messages per month sent more than 48 hours after the user's last interaction (paid replies).

Output Schema

NameRequiredDescriptionDefault
notesYes
plansYes
reasonYes
disclaimerYes
affiliationYes
recommendedYes
data_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, so safety is covered; the description adds genuinely new context: prices include 10% VAT, the plans are those in force from 1 June 2026, the Cơ bản price is unpublished by Zalo, and the tool is 'reference only'. It also discloses that results include a reason and the paid-reply overage. It does not say whether prices are monthly or the currency, leaving a small gap.

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

Conciseness3/5

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

The core purpose is front-loaded, but the main body is a single long run-on sentence that packs plan names, VAT, feature lists and a parenthetical parameter recap into one breath. The parameter listing duplicates the schema, and splitting the sentence would materially improve scanability.

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 read-only selector with an output schema, full annotation coverage and 100% documented parameters, the description supplies the missing framing: pricing basis, effective date, the unpublished Cơ bản price and a reference-only caveat. Currency and billing period (monthly vs. term payment) are the only notable omissions.

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?

Schema coverage is 100%, so the baseline is 3; the description goes slightly beyond by grouping the six inputs as a needs profile and by giving worked examples that clarify defaults (staff 8, replies 3000 with chatbot and a 6-month term). Most per-parameter meaning (the needs_api implication, the 6-month restriction to Tăng trưởng/Toàn diện) is already in the schema and is merely restated.

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 — comparing the four named Zalo OA plans effective 1 June 2026 — and a concrete decision goal: pick the smallest plan meeting stated needs. An agent can immediately tell this is a plan-selection/recommendation tool, distinct from cost-estimation or channel-choice siblings.

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 makes the use case explicit ('pick the smallest plan that meets your needs') and supplies three example invocations, including an empty object, which reveals it works as a discovery call. It never states when not to use it or names a sibling alternative such as estimate_message_cost, so it stops short of a 5.

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.