Skip to main content
Glama

删除话题

app_delete_session

Permanently deletes a specified archived session or current topic record in SideDesk, letting users clear unwanted conversation data from the UI.

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_delete_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose two important traits: the deletion is permanent and irreversible ('永久删除'), and the tool is intended for UI use only. It says nothing about the effects on associated data or what happens if the session is missing, which would round it out.

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?

This is a single tight sentence with the usage qualifier front-loaded ahead of the action, and it wastes no words. The terseness is appropriate in form, but it is partly achieved by omitting details that an agent would need.

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 destructive one-parameter tool with no annotations and no output schema, the description covers the action and its irreversibility, which is the most important part. It lacks confirmation or error behavior, the scope of what else is removed, and any sessionId semantics, leaving real gaps.

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?

The schema has 0% description coverage, so the single required parameter sessionId has no documented meaning in the schema. The description implies that sessionId refers to an archived or current topic record, but it does not clarify the accepted format or how an archived record is addressed compared with the current one.

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 clear verb-resource pair: 永久删除 (permanently delete) applied to 话题/会话记录, with the scope narrowed to the archived or current topic ('指定归档或当前话题记录'). It does not name any sibling such as app_clear_session, so the distinction between 'delete' and 'clear' is left for the agent to infer.

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 leading phrase 'UI 专用' (UI-only) is a real usage constraint, and it tells an automated agent that this is a GUI-facing action rather than a general-purpose one. Still, no alternative is named and no preconditions are stated, so the when-to-use guidance amounts to an implied restriction.

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