Skip to main content
Glama

面灵AI 面试助手

get_wechat_support_link

Read-only

获取用户专属的微信客服链接,用户在微信中打开即可与客服对话,对话自动关联其账号。链接三天内有效。(需要用户授权,范围 account:read)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=true, destructiveHint=false), the description discloses that the call requires user authorization with the account:read scope and that the link expires after three days—both material facts an agent could not infer from the schema. It does not state whether repeated calls return the same link or reset the expiry, and gives no rate-limit or failure behavior.

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?

A single compact sentence with the core purpose front-loaded, followed by what the link does, its expiry, and the auth requirement. Every clause carries distinct information with no filler.

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 read-only tool with no output schema, the description covers purpose, authorization scope, and link lifetime—enough to call it correctly. It stops short of describing the response shape (e.g., whether the payload is a plain URL) or the behavior on repeat calls, which would complete the picture.

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 no parameters, so the baseline is 4 and there is nothing for the description to clarify beyond confirming the call is unconditional for the authenticated user.

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 names a specific verb and resource: fetch the user's dedicated WeChat customer-service link, and explains what the link does (opens a chat in WeChat auto-associated with the account). It is clearly distinguishable from siblings such as get_purchase_link or get_account, though it does not explicitly route against them.

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?

The usage scenario is implicit but clear: call this when the user needs to reach human customer service via WeChat, and the resulting link is meant to be opened inside WeChat. There are no explicit exclusions or named alternatives, so it falls short of the top band.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources