Skip to main content
Glama

解绑当前话题继承摘要

app_clear_inherited_summary

Removes the inherited summary for the current topic so subsequent turns stop injecting prior conversation summaries. Use it to reset carried-over context and keep later responses scoped to current input.

Instructions

UI 专用:移除当前话题的 inheritedSummary,后续轮次不再注入前序摘要。

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

Input Schema

NameRequiredDescriptionDefault
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations at all, the description carries the burden and does disclose what is removed (inheritedSummary on the current topic) and the downstream consequence (prior summaries stop being injected in later turns). It omits reversibility, behavior when nothing is bound, and any permission/error conditions.

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?

One short sentence with the 'UI 专用' qualifier front-loaded, followed by action and consequence; nothing is redundant.

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 one-parameter mutation with no annotations and no output schema, the description covers purpose and effect adequately but leaves the parameter unexplained and says nothing about the no-op case or response behavior.

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% and the single parameter sessionId is never mentioned; '当前话题' only loosely implies the session context. The description must compensate here and does not explain how sessionId maps to the topic whose summary is cleared.

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 names a specific verb+resource ('移除当前话题的 inheritedSummary') and states the resulting effect ('后续轮次不再注入前序摘要'), which distinguishes it from app_update_inherited_summary. It is clear but does not explicitly name the sibling it differs from.

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 专用' scopes usage to UI-driven flows and the effect clause hints at when the result matters, but there is no explicit when-to-use vs. when-to-use-instead guidance (e.g., versus app_update_inherited_summary or app_clear_session).

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