Skip to main content
Glama

更新当前话题继承摘要文本

app_update_inherited_summary

Update the inherited summary at the top of the current topic so users can fine-tune what context carries forward in the SideDesk assistant.

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>",
      "summary": "<summary>"
    },
    "name": "app_update_inherited_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
summaryYes
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It implies a mutation of existing summary text but never says whether the previous content is overwritten or merged, whether the change is reversible, or what permissions/preconditions apply.

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?

A single tight sentence with the UI-only qualifier front-loaded, so nothing is wasted. It is short because it omits detail rather than because it is efficient.

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?

For a two-required-parameter mutation with no annotations, no output schema and no documented parameters, the description leaves the agent without enough to call it safely. Overwrite semantics, session scope, and return behavior are all unaddressed.

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%, so the description must compensate and does not. It hints at the summary payload, but never explains that sessionId identifies the topic/session whose inherited summary is being edited, nor any format or length expectations for summary.

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 concrete action (update/fine-tune) and a concrete resource (the inherited summary at the top of the current topic), which distinguishes it from the sibling app_clear_inherited_summary by implication. It never explicitly contrasts the two, so differentiation relies on the agent reasoning about the verb.

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) is a real usage restriction that tells an agent this is meant to be driven by a UI surface rather than general automation. There is no guidance on when it should not be called, and no named alternative such as the clear-summary sibling.

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