Retrieve Mini App metadata, quotas, and versions from Zalo Developer API to inspect app limits, status, and deployment details.
Retrieve Mini App metadata, quotas, and versions from Zalo Developer API.
| Name | Required | Description | Default |
|---|---|---|---|
| appId | No | Optional Mini App ID override. | |
| token | No | Optional token override. | |
| projectDir | Yes | Absolute path to the project directory. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. 'Retrieve' implies a read-only operation and it names the source API, but it does not disclose authentication requirements, rate limits, error behavior, or any other operational details.
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?
A single sentence that is front-loaded with the verb and resource, and contains no wasted words.
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?
The schema fully documents parameters and no output schema exists, so the description's broad mention of returned data (metadata, quotas, versions) is useful. However, it omits usage context and behavioral details that would fully orient an agent for a read-only retrieval tool.
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?
Schema description coverage is 100%, so the schema already documents all three parameters. The description adds no parameter-level syntax or format details beyond what the schema provides, making 3 the appropriate baseline.
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?
States a specific verb ('Retrieve') and resource ('Mini App metadata, quotas, and versions') plus the source API ('Zalo Developer API'). It clearly distinguishes itself from write-oriented siblings like create_app, build, and deploy, though it does not explicitly name them.
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?
Provides no when-to-use guidance, no alternatives, and no prerequisites. An agent must infer that this is for inspecting app information rather than managing login, building, or deploying.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.