Skip to main content
Glama
lychee20000105

wechat-miniapp-engineering-mcp

miniapp_dev_recovery_playbook

Diagnose and resolve common WeChat Mini Program development failures with recovery playbooks for session state, missing pages, cloud routes, DevTools errors, and release issues.

Instructions

把微信小程序开发中的常见故障复盘成恢复手册,覆盖会话错乱、页面四件套、云函数路由、DevTools EISDIR、版本发布和外发确认。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNo只看某类问题,默认 all。
includeCaseStudyNo是否包含本次复盘摘要,默认 true。
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It describes a read-only generation of a recovery manual, but does not mention any side effects, permissions needed, or return format. Minimal information beyond the basic function.

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?

The description is a single, front-loaded sentence that efficiently conveys the tool's purpose and scope. Every word earns its place with no redundancy.

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?

The tool has no output schema, so the description should clarify the output format. While it describes the generated manual's coverage, it does not specify whether it returns plain text, markdown, or JSON. Context is mostly complete given the sibling tools landscape.

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 coverage is 100%, and the description adds no extra semantic beyond the schema's parameter descriptions. The description merely restates that topic filters by issue type and includeCaseStudy controls summary inclusion.

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 clearly states the tool's function: compiling common WeChat mini-program faults into a recovery manual. It specifies the covered topics (session confusion, missing page files, etc.), making it distinct from sibling tools like miniapp_launch_checklist or miniapp_security_quick_scan.

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

Usage Guidelines3/5

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

The description implies usage for troubleshooting common faults but does not explicitly state when to use this tool over alternatives. No exclusions or when-not-to-use guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lychee20000105/wechat-miniapp-engineering-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server