Skip to main content
Glama

重命名话题

app_rename_session

Rename a specified session or topic by supplying its session ID and new title. Use it to update displayed labels in SideDesk’s 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>",
      "title": "<title>"
    },
    "name": "app_rename_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/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 of behavioral disclosure. It implies a mutation but says nothing about whether the rename persists, whether it requires the session to be idle, whether concurrent/duplicate titles are allowed, or what errors occur for an unknown sessionId. The 'UI 专用' note is the only behavioral signal, and it is unexplained.

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 short sentence with the UI-only qualifier front-loaded and no filler. It is efficient but borders on under-specification rather than being genuinely economical, since nothing about the operation's effects is stated.

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?

This is a simple two-parameter tool with no output schema, so the bar is low, and the description covers the core intent plus a UI-only caveat. It still omits return behavior, permission/precondition requirements, and any validation rules for the title, which an agent would need before invoking it confidently.

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?

Schema description coverage is 0% and both parameters are required, so the description must compensate. '修改指定话题的标题' does implicitly map sessionId to the target session and title to the new title, and it clarifies that title replaces rather than appends. It does not, however, mention any constraints on title (length, uniqueness, trimming) or what happens with an invalid sessionId.

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 action and target: modify the title of a specified topic/session, which maps clearly onto the tool name app_rename_session. No sibling in the catalog performs renaming, so the risk of confusion is low. The only weakness is the loose terminology '话题' (topic) versus the parameter's 'sessionId', which leaves a small ambiguity about whether a topic and a session are the same object.

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 'UI 专用' (UI-only) prefix is a real usage constraint: it tells the agent this is not intended for programmatic/automation flows. However, it does not say when an agent should rename a session versus creating a new one (app_new_session) or otherwise editing it, and no exclusions or alternatives are named.

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