Skip to main content
Glama
Sign In
alidocs-web-mcp

alidocs-web-mcp

by magical-index
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

撤销连接

revoke_session

Invalidate the current pairing code and disconnect the page session to end authorization or respond to a suspected code leak. Requires re-pairing via get_pairing_code before reconnecting.

Instructions

轮换配对码并断开当前页面会话（S11）。撤销后旧配对码立即失效，页面 sessionStorage 里的旧值无法再重连，需重新调用 get_pairing_code 配对。用于结束一次授权或怀疑配对码泄露时。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.7/5.0
Behavior5/5

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

注释声明readOnlyHint=false和openWorldHint=false，描述详细说明了副作用：旧配对码失效、sessionStorage值无法重连，以及需要重新配对。无矛盾，且额外披露了内部标识S11。

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?

两句话传达了目的、副作用、使用场景和后续步骤，无冗余信息，结构清晰。

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

Completeness5/5

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

对于零参数工具，描述已涵盖功能、副作用、使用场景和后续操作，无输出模式但描述足够。兄弟工具列表提供了上下文，无缺失信息。

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?

工具无参数，模式覆盖率为100%，描述无需解释参数。基准为4，描述中提及需要重新调用get_pairing_code，但那是后续步骤，不影响此维度。

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?

描述明确说明了动词（轮换、断开）和资源（配对码、页面会话），并区分了兄弟工具（get_pairing_code等）。明确表示撤销后旧配对码失效，会话断开。

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?

描述了使用场景（结束授权或怀疑泄露），并指出需要重新调用get_pairing_code配对。但未显式说明何时不使用，不过基于兄弟工具列表，其他工具不执行撤销操作，因此清晰度足够。

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