Skip to main content
Glama

清空话题消息

app_clear_session

Clears the conversation history for a specified session and resets the thread, enabling a fresh topic in SideDesk.

Instructions

UI 专用:清空指定话题的对话记录并重置线程。

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": {
      "sessionId": "<sessionId>"
    },
    "name": "app_clear_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 disclosure burden. It does tell the agent that conversation history is erased and the thread is reset, which is the key destructive consequence, but it omits reversibility, whether the session object itself survives, and any permission or confirmation requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with the scope qualifier ('UI 专用') front-loaded and no filler. It is efficient, though the terse phrasing leaves little room for the missing behavioral and parameter detail.

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?

The tool is simple (one parameter, no output schema, no nested objects), so the description does not need to be long. Still, it leaves the only parameter undefined and does not say what state remains after the reset, which is information an agent needs before invoking a destructive-sounding operation.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter, so the description should compensate. It only says '指定话题' (specified topic), never explicitly linking that to the sessionId parameter or describing its format, so the parameter remains essentially undocumented.

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 in '清空指定话题的对话记录并重置线程' (clear a specified topic's conversation records and reset the thread), which is more precise than the title alone. However, it does not distinguish this tool from siblings that also act on sessions, such as app_delete_session or app_compress_session.

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?

'UI 专用' (UI-only) gives an implied usage boundary: this tool is intended for interface-driven use rather than general agent calls. Beyond that marker, there is no explicit when-to-use, when-not-to-use, or named alternative, so the caller must infer the choice between clearing, compressing, and deleting a session.

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