Skip to main content
Glama

SideDesk · 副席

sidedesk_open

Open or refresh the right-side SideDesk panel to view dual-engine character cards, running tasks, and pending shadow-copy diffs for review, optionally focusing on a specific session.

Instructions

打开或刷新右侧 SideDesk · 副席面板,查看双引擎人物卡、运行中任务与待验收的影子副本 Diff。支持空参数调用。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sidedesk_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdNo可选:聚焦到指定副席会话 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the panel side, what content appears, and that no arguments are required, which implies a safe, idempotent refresh. It does not state what happens with an unknown sessionId, whether the panel state is replaced or merely re-rendered, or whether this has any side effects on the running tasks it displays.

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 compact sentence with the action front-loaded, followed by the content inventory and the empty-parameter note. Every clause carries information, though the content enumeration is somewhat dense and the trailing note could be phrased as a usage condition rather than a bare capability.

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

Completeness4/5

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

This is a low-complexity, zero-required-parameter UI tool with no output schema, and the description covers action, target, and visible content. Given the simplicity, the remaining gaps (invalid sessionId behavior, side effects) are minor rather than disqualifying.

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 100% for the single optional sessionId, and the schema already explains that it focuses a specific sub-session. The description never mentions sessionId, so it adds no meaning beyond the schema. The baseline of 3 applies when the schema does all the work.

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 verb pair ('打开或刷新' — open or refresh) and a specific resource (the right-side SideDesk panel), then enumerates what the panel surfaces (dual-engine persona cards, running tasks, pending shadow-copy diffs). This is far more than a restatement of the name. It stops short of explicitly differentiating itself from siblings such as sidedesk_job_status or app_get_diff, which also expose task/diff views.

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?

Usage is only implied: the agent can infer it should call this to bring up or refresh the panel before inspecting state. The one explicit guideline is '支持空参数调用' (empty-parameter invocation is supported), which is useful but operational rather than a when-to-use rule. No exclusions or named alternatives are given, so the agent must guess whether to call this versus a sibling that reads the same data directly.

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