Skip to main content
Glama

Zalo Business Reference (ZBS Template Message, OA)

Zalo error code lookup

error_lookup
Read-onlyIdempotent

Explain a Zalo error code in plain words: which table it comes from (ZBS Template Message, the archived ZNS table, or the Official Account API; the same code can mean different things in different tables) and what to check. A positive number is also tried as negative. Examples: {"code":-133}; {"code":-100,"table":"oa_api"}; {"code":249}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>"
    },
    "name": "error_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesError code returned by Zalo, e.g. -133 (a positive number is also tried as negative).
tableNoLimit to one table: zbs (ZBS Template Message), zns_archive (old ZNS), oa_api (Official Account API).

Output Schema

NameRequiredDescriptionDefault
codeYes
foundYes
matchesYes
disclaimerYes
affiliationYes
data_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context that a positive number is also tried as negative and that interpretation is table-dependent, though it does not describe output shape or failure behavior when a code is unknown.

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?

One sentence explains meaning and table dependence, then a second sentence gives three concrete examples. It is front-loaded and every clause adds decision-relevant information with no filler.

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?

The tool is a simple two-parameter read lookup with a full output schema, so return values need not be explained. The description covers purpose, table ambiguity, fallback behavior, and examples—everything needed to invoke it correctly.

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 description coverage is 100% and already documents both parameters, including the enum meanings and the positive/negative fallback. The description reinforces the negative-fallback behavior and table dependency, but adds little syntax or semantics beyond the schema, so baseline 3 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?

The description states a specific verb (explain) and resource (a Zalo error code), and even names the three distinct tables a code may belong to. An agent can distinguish this lookup tool from siblings like validate_template or check_sending_rules without inspecting the schema.

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 gives concrete call examples and states the key usage condition: the same code can mean different things in different tables, so use the table parameter to narrow. It stops short of saying when to prefer this over other diagnostic siblings or what to do when no table is known.

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.