Skip to main content
Glama

列出副席人物卡

sidedesk_list_personas

Lists all personas configured in SideDesk, showing each persona's engine type, model, and permissions while excluding secret values.

Instructions

列出 SideDesk 中配置的所有人物卡(含驱动引擎类型、模型与权限),绝不返回任何密钥。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It usefully discloses the shape of the payload (engine type, model, permissions) and a security guarantee that no secrets/keys are ever returned, but it says nothing about ordering, result size, or whether the list can be empty.

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?

A single sentence with no waste: the resource is front-loaded, the returned fields follow, and the no-secrets guarantee closes it. Nothing is repeated from the schema.

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?

For a zero-parameter read tool with no output schema, the description covers the essentials by enumerating key returned fields and ruling out secret exposure. It stops short of describing result structure or ordering, which is the only remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning for the description to add. The description's mention of '所有' correctly reinforces that no filtering arguments exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('列出 ... 所有人物卡') and scopes it ('SideDesk 中配置的'), then names the fields returned (驱动引擎类型、模型、权限). That is enough for an agent to distinguish a read-only enumeration from the save/delete persona siblings without opening any schema.

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 implied rather than stated: an agent can infer this is the discovery call before app_save_persona or app_delete_persona, but the description never says when to call it or when not to. The word '所有' signals no filtering is available, which is the only routing hint present.

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