Skip to main content
Glama

保存用户个人资料

app_save_user_profile

Saves your display name, avatar, and light/dark theme preference to the plugin directory, then injects your custom name into both engine instructions.

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

Input Schema

NameRequiredDescriptionDefault
userNameNo
themeModeNo
userAvatarNo

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 provided, so the description carries the full burden. It does earn credit for two non-obvious disclosures: data goes to a plugin persistence directory, and a custom 称呼 is auto-injected into dual-engine instructions (a real side effect). However, it never says whether all three params are optional, whether omitting one erases the stored value, or what a save returns — critical for a mutation tool with 0% annotation coverage.

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 semicolon-joined sentence with the 'UI 专用' scoping caveat front-loaded, then the payload, then the side effect. Nothing is padded, though the semicolon packs two distinct ideas that could read more cleanly as separate statements.

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 simple three-optional-param save with no output schema, the definition covers what is stored, where, and one downstream effect, which is most of what an agent needs. The remaining gap is merge-vs-overwrite semantics for the optional fields.

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%, so the description must compensate; it maps all three params to concepts (userName→称呼, userAvatar→头像, themeMode→外观主题偏好) and flags that 称呼 is injected elsewhere. It adds nothing on the enum values for themeMode, empty-string vs null handling, or whether partial updates are allowed.

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 names a specific verb (保存/save) plus three concrete resources — 称呼, 头像, 外观主题偏好 — and the destination (插件持久化目录). The 'UI 专用' prefix further scopes it away from backend/agent-facing saves, though it never names the overlapping siblings app_set_theme or app_save_persona explicitly.

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 this is the UI-side write path, which is an implied usage signal, but the agent is left guessing whether it may call it at all and when to prefer it over app_set_theme (which appears to also set appearance). No when-not-to-use case or alternative is stated.

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