Skip to main content
Glama

获取小程序系统信息

wdt_system_info
Read-only

Retrieves WeChat mini program system information via miniProgram.systemInfo(), helping AI agents inspect device, OS, screen, and runtime details for automation decisions.

Instructions

返回 miniProgram.systemInfo()。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wdt_system_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so safety is covered. Beyond that the description adds nothing: it does not say what the returned object contains, whether it requires an active session, or how it behaves if no mini program is open — it merely restates the API name.

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

Conciseness3/5

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

It is one short sentence with no filler, but the brevity reflects under-specification rather than efficiency — an API reference is substituted for a description, leaving the agent to infer the value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should describe the shape of the returned systemInfo object (platform, SDK version, screen size, etc.) since that is the tool's entire output. It does none of that, leaving a read tool whose return value is completely undocumented.

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?

The tool takes zero parameters, so the baseline is 4. There is no parameter semantics for the description to clarify, and it correctly implies a no-argument call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the underlying API call (miniProgram.systemInfo()) and implies it returns system information, but never states in plain language what the tool does or what 'system info' covers. It only distinguishes itself from siblings for an agent that already knows the WeChat DevTools API surface.

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

Usage Guidelines2/5

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

No when-to-use, prerequisites, or alternative guidance is given. Nothing indicates when an agent should call this instead of the generic wdt_wx_method, or whether a connection/login must exist first.

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