Skip to main content
Glama

获取副席面板状态

app_get_state

Retrieves redacted persona cards, session data, live task streams, pending shadow copies, and revocable backups to render the SideDesk UI state.

Instructions

UI 专用:拉取脱敏后的人物卡、会话、实时任务流、待验收影子副本与可撤销备份。

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": "app_get_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
personaIdNo
sessionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 disclosure burden. It does contribute genuinely behavioral information: the data is 脱敏 (redacted/desensitized) and it is a composite snapshot covering five payload classes, which is valuable because no output schema exists. However, it does not state the safety profile (read-only, no side effects), pagination or size limits, or freshness of the 'real-time' stream.

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?

The description is one front-loaded sentence: the qualifying constraint 'UI 专用' comes first, followed by the payload enumeration. Nothing is redundant, though packing five items into one Chinese-comma clause makes it dense rather than scannable.

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 two-optional-parameter read tool with no output schema and no annotations, the definition names the returned payload categories but does not describe their structure, the effect of the optional scope parameters, or the safety profile. It is adequate to recognize the tool's purpose but not complete enough to invoke it confidently with or without parameters.

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?

Both parameters (personaId, sessionId) have 0% schema description coverage, so the schema adds no meaning and the description must compensate by explaining them. The description never mentions either parameter, so an agent cannot tell whether omitting them returns a global snapshot or an empty result. It only obliquely implies scoping through the noun list.

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 gives a specific verb (拉取, "pull") and an explicit list of resources returned: persona cards, sessions, live job stream, pending-acceptance shadow copies, and revocable backups. This is far more concrete than a bare restatement of the title 获取副席面板状态, though the definition never contrasts itself with siblings such as app_get_diff or sidedesk_job_status.

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 专用' prefix is a real constraint for when to use it: it signals UI dashboard consumption rather than agent-side mutation. However, the definition does not say when to prefer it over app_get_diff, sidedesk_job_status, or per-resource getters, nor does it explain what the optional scope parameters select. Usage is therefore implied rather than stated.

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