Skip to main content
Glama

检查开发者工具登录状态

wdt_is_login
Read-only

Verifies whether WeChat DevTools is currently logged in via the official CLI, helping you confirm authentication before previewing or uploading a mini program.

Instructions

调用官方 CLI islogin,返回当前是否已登录。预览和上传前建议先检查。

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_is_login"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare `readOnlyHint=true` and `openWorldHint=true`, so the safety profile is covered; the description confirms the read-only nature by framing the tool as a query that reports login state and identifies the underlying CLI invocation. It does not describe the return shape (boolean vs. object), error behavior, or whether the call can block, so it adds only modest context beyond the annotations.

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?

Two short sentences with no waste: after reading the first sentence, the agent knows what the tool does; the second adds usage guidance. The purpose comes before the recommendation, so the key information is front-loaded.

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 zero-parameter status probe with no output schema, the description says enough for an agent to invoke it and interpret the result as a login check. A note on the exact return type and on what to do when the check fails would have made it complete.

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 there is nothing for the description to disambiguate; the schema is empty and fully covered. The baseline for a parameterless tool applies.

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 specific verb and resource: it calls the official CLI `islogin` and returns whether the user is currently logged in. This makes the tool clearly a status check rather than an authentication action, which implicitly distinguishes it from the sibling `wdt_login` without naming it.

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 concrete when-to-use guidance: "预览和上传前建议先检查" (check before preview and upload), which ties the call to the sibling tools `wdt_preview` and `wdt_upload`. It does not state when the check is unnecessary or what to do on failure, so it falls short of full alternative routing.

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