Skip to main content
Glama

删除人物卡

app_delete_persona

Deletes a specified persona card by ID, allowing UI-only removal of unwanted persona entries in SideDesk.

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": {
      "id": "<id>"
    },
    "name": "app_delete_persona"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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. "Delete" is destructive by nature, yet the description does not say whether removal is permanent, whether confirmation or specific permissions are required, how sessions that reference the persona are affected, or what happens when the id does not exist.

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 purpose and the UI scoping constraint front-loaded, containing no filler. It is terse to the point of under-specification, but that is a completeness problem, not a verbosity problem.

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 one-parameter destructive tool with no annotations and no output schema, the description should say more about irreversibility, preconditions, and return or error behavior. Given the low tool complexity, however, the gap is not as severe as it would be for a multi-parameter tool.

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?

The tool has one required parameter (id) with 0% schema description coverage, so the description must explain that parameter. "指定人物卡" only hints that id identifies the persona, without adding format or source details beyond the field name.

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 uses a specific verb (删除, delete) plus resource (指定人物卡, the specified persona card), and the "UI 专用" marker hints that this tool belongs to UI flows rather than ordinary agent calls. It does not name a sibling such as app_save_persona or sidedesk_list_personas, so the agent must infer differentiation from the name alone.

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 专用" implies the tool is restricted to UI context and therefore that agents generally should not call it directly, which is implicit when-to-use guidance. However, no alternative is named for the case where an agent needs to remove a persona, and no preconditions are stated.

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