Retrieves the currently displayed page in WeChat Developer Tools and sets it as the active page for subsequent automation commands.
获取当前页面信息并设置为活动页面
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| code | Yes | ||
| data | Yes | ||
| meta | Yes | ||
| error | Yes | ||
| warnings | Yes | ||
| nextActions | Yes | ||
| observation | Yes | ||
| partialData | Yes | ||
| schemaVersion | Yes |
Changes observed during successful MCP inspections.
v0.7.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. It discloses a meaningful side effect ('设置为活动页面') beyond what the name alone conveys. It does not explain what 'active page' means or what information is returned, but the output schema is available to cover return values.
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 concise Chinese sentence that front-loads the main action and then adds the side effect. Every word earns its place, with no redundancy or filler.
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?
Given zero parameters and the presence of an output schema, the description covers the core behavior and side effect adequately. The main missing detail is the semantics of 'active page' and how this relates to sibling page/snapshot tools, but that is a minor gap for this simple 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?
The input schema has zero parameters and schema description coverage is effectively 100%, so there is nothing for the description to add. The baseline of 4 applies because there are no parameter semantics to clarify.
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?
The description names a specific verb ('获取') and resource ('当前页面信息'), and adds a distinct behavior ('设置为活动页面') that helps differentiate it from siblings like get_page_snapshot. It is clear about what the tool does, though it does not explicitly distinguish itself from related tools.
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?
Usage is implied by the described behavior: call this when you want current page information and to mark it as active. However, it gives no explicit when-to-use guidance, exclusions, or alternatives, so an agent must infer the appropriate context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.