Skip to main content
Glama

开启新副席话题

app_new_session

Starts a new conversation for a chosen persona and project directory, archives the prior thread, and can inherit a compressed context summary.

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": {
      "personaId": "<personaId>",
      "sourceDir": "<sourceDir>"
    },
    "name": "app_new_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
personaIdYes
sourceDirYes
inheritSummaryNo
sourceSessionIdNo
summarizerPersonaIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations exist, so the description must carry behavior itself; it does disclose two valuable non-obvious traits — the old topic is archived rather than destroyed, and summary inheritance is quota-free when a fresh summary exists. It says nothing about the return value (new session identifier?), permissions, or what happens to in-flight work in the old topic, which is a meaningful gap for a 6-parameter mutation tool with no annotations and no output schema.

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 dense sentence with the UI-only caveat front-loaded followed by the archive behavior and the optional inheritance. Parenthetical qualifiers carry real information rather than padding, though the sentence is packed enough that it reads as a run-on.

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

Completeness2/5

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

With six undocumented parameters, no annotations, and no output schema, the definition leaves too much unstated: what the call returns, whether sourceSessionId is required for inheritance, and what summarizerPersonaId governs. The purpose and lifecycle are covered, but the invocation surface is not.

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% across six parameters, so the description must compensate. It clarifies personaId (人物卡), sourceDir (工程目录), and partially inheritSummary/摘要 reuse, but title, sourceSessionId, and summarizerPersonaId receive no explanation at all — the agent cannot tell what sourceSessionId selects or when summarizerPersonaId is needed.

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 combines a specific verb (开启全新话题) with two resources (指定人物卡 + 工程目录) and clarifies the lifecycle relation to the old topic (旧话题保留归档). It is clearly distinct from destructive siblings such as app_delete_session or app_clear_session, though it never names an alternative explicitly.

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 专用」imposes a real constraint on where this tool may be used, which is more than most definitions offer, but it is not spelled out as when-to-use versus when-to-use-instead (e.g. versus app_clear_session or app_compress_session). The optional inheritance path is described as a condition (已有新鲜摘要时), which helps, but no explicit exclusions are given.

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