Skip to main content
Glama
Sign In
wx-mp-mcp

wx-mp-mcp

by k98crypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

List sandbox modules

mp_sandbox_modules

Lists all module paths registered in a WeChat Mini Program bundle to locate SDK signature modules; run mp_analyze first and pass bundle_paths to coordinate main and subpackage bundles.

Instructions

列出小程序 bundle 中注册的所有模块路径。用于发现 SDK 签名模块位置。需要先 mp_analyze 解包。分包签名 SDK 依赖主包 runtime 时用 bundle_paths 传[主包,分包]协同加载。

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": {
      "appid": "<appid>"
    },
    "name": "mp_sandbox_modules"
  }
}

Input Schema

NameRequiredDescriptionDefault
appidYes小程序 appid
bundle_pathNo自定义 app-service.js 路径 (默认按 appid 自动查找)
bundle_pathsNo多 bundle 协同加载[主包,分包,...]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the behavioral burden. It discloses the important prerequisite (must unpack first) and the multi-bundle coordinated-loading behavior, which is genuinely useful. However, it never states read-only/safety profile, whether the call is cheap or expensive, or what the result looks like, leaving real gaps for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the core purpose, then the discovery use case, then the prerequisite, then the edge-case parameter guidance. Nothing is redundant, though the ordering separates the prerequisite from the action it gates.

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 three-parameter, annotation-free listing tool with no output schema, the description covers purpose, prerequisite, and the tricky multi-bundle parameter, which is the main thing an agent could get wrong. Return-value shape is left implicit, which is acceptable for a list operation but is a small remaining gap.

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?

Schema description coverage is 100%, so the baseline is 3, but the description earns above baseline by explaining the non-obvious semantics of bundle_paths: it is for the case where a subpackage signature SDK depends on the main-package runtime, passed as [main, subpackage]. It adds no such extra meaning for bundle_path and only partially covers appid.

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 states a concrete verb and resource: list all module paths registered in the mini-program bundle, and adds the intent (discover SDK signature module locations). That is far more specific than the title alone. It does not explicitly contrast with sibling listing tools (mp_sandbox_export, mp_list_apps), so it falls short of a 5.

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 a clear precondition (mp_analyze must unpack the bundle first) and a use case (finding SDK signature modules), plus a specific conditional rule for bundle_paths when a subpackage signature SDK depends on the main-package runtime. There are no explicit exclusions or named alternatives, so a 4 rather than a 5.

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

Deploy Server

Other Tools