Skip to main content
Glama
Sign In
yuketang-mcp

yuketang-mcp

by powercess
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

退出登录

ykt_logout

Clears the locally stored session for a specified Yuketang region without affecting login status on other devices.

Instructions

删除本地保存的会话。不会影响其他设备上的登录状态。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "region": "<region>"
    },
    "name": "ykt_logout"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionYes要清除的区域

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/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 does disclose one genuinely useful behavior: the logout is local-only and 不会影响其他设备上的登录状态. However, it says nothing about whether a server-side session is invalidated, whether the action is reversible, or whether authentication is required first, which are material gaps for a logout tool.

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 zero filler, and the most important behavioral fact (local-only scope) is front-loaded right after the action.

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

Completeness3/5

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

For a single-parameter, no-annotation, no-output-schema tool, the description covers the core action and its cross-device scope. It is still incomplete because it leaves the required region parameter, with its non-obvious enum values, entirely unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description does not mention the region parameter at all, and the enum values (hetang, changjiang, huanghe) are opaque; a sentence explaining that region selects which platform or tenant's session is cleared would have added real value.

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 gives a specific verb and resource (删除本地保存的会话), which makes it clear that the tool logs out by removing the local session. It is obviously the inverse of ykt_login, but it never names a sibling or explicitly states that it ends the current login, so differentiation relies on inference from the name.

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 intended use is implied by the tool name and the word 会话, but the description never says when to call this instead of, for example, ykt_status or ykt_login, and it states no prerequisites. The agent must infer usage from the name alone.

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