Skip to main content
Glama

Zalo Business Reference (ZBS Template Message, OA)

Zalo reference data: sources and gaps

data_info
Read-onlyIdempotent

Return the data version and retrieval date, the official Zalo pages used, what Zalo does not publish (Cơ bản plan price, broadcast price above the free allowance, Mini App fees, the VAT rate for template messages, and others), where Zalo's own pages disagree (maximum buttons, night window, OTP by UID, old fallback prices) and how this tool resolves it, the change log and the worked example. Use when the user asks how current or reliable the figures are. Takes no arguments: {}.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
sourcesYes
data_dateYes
disclaimerYes
affiliationYes
data_versionYes
discrepanciesYes
not_publishedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses that unpublished items are enumerated, that internal disagreements exist (buttons, night window, OTP by UID, fallback prices) and that the tool states how it resolves them. It does not describe size or shape of the response, though an output schema exists.

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 is front-loaded, but the whole definition is a single ~70-word sentence with deeply nested parentheticals listing five unpriced items and four disputed values. That detail overlaps heavily with what the output schema already documents, making it harder to scan than a short purpose sentence plus a separate usage line.

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 no-argument, read-only metadata tool with an output schema and full annotations, the description is complete: trigger, scope, and the fact that gaps and conflicts are surfaced are all stated. The only minor gap is not indicating roughly how large or structured the returned report is, which the output schema likely covers.

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?

Zero parameters, and the description explicitly confirms this with 'Takes no arguments: {}', removing any doubt about whether a query or locale must be supplied. Baseline for a no-parameter tool applies; nothing further is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a concrete verb and resource ('Return the data version and retrieval date, the official Zalo pages used...') and enumerates the exact contents: gaps, disputed values, change log, worked example. That is specific enough to separate it from calculation siblings like estimate_message_cost or oa_plan_compare, though the purpose is conveyed as an inventory list rather than a single crisp statement of what the tool is for.

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?

It gives an explicit trigger: 'Use when the user asks how current or reliable the figures are.' That clearly routes provenance/currency questions here rather than to the pricing or validation siblings. It stops short of naming alternatives or stating when not to call it (e.g. when the user actually wants a price).

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.