Skip to main content
Glama
Sign In
WeCom MCP Server

WeCom MCP Server

by atttx123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

check_config

Avoid WeCom setup errors by verifying configuration readiness without network requests. Confirm setup is complete before using messaging tools.

Instructions

检查当前 WeCom 配置是否就绪 (不发起网络请求)。

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": "check_config"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses a key behavioral trait (no network requests), which is useful context, but it does not mention whether the check is read-only, what 'ready' means, or what happens if the config is not ready. Lacks fuller transparency.

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 in Chinese that states the purpose and a key behavioral caveat. Every word earns its place; no fluff or 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?

Given zero parameters and an output schema, the description is adequate. It covers the tool's core function and adds a behavioral note. It could briefly mention when to use it, but overall the tool is simple and well-described.

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 has zero parameters, so the baseline is 4. The description does not need to add parameter details, and the schema correctly defines an empty object, so no gaps exist.

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 checks current WeCom configuration readiness. The verb '检查' (check) and resource '当前 WeCom 配置' are specific, and it is clearly distinct from the sibling tools which all send messages or look up users.

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 does not explicitly state when to use this tool versus alternatives, but the phrase '不发起网络请求' (does not initiate network requests) implies it is a safe, local pre-flight check. No exclusions or alternative tool names are mentioned, so guidance remains implicit.

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