Skip to main content
Glama

切换外观主题

app_set_theme

Persists the chosen UI theme mode—auto, light, or dark—so the selected appearance remains after the panel closes.

Instructions

UI 专用:轻量持久化外观主题模式(auto 跟随宿主 / light 浅色羊皮纸 / dark 深色暖炭),防关面板丢失。

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": {
      "themeMode": "<themeMode>"
    },
    "name": "app_set_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeModeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 burden. It usefully discloses the persistence behavior and that the setting survives closing the panel ('防关面板丢失'), which is exactly the kind of trait an agent cannot infer from the schema. It stops short of saying whether this persists server-side vs client-side, whether it is reversible, or what happens on invalid/unsupported themes.

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?

One compact sentence, front-loaded with the scope qualifier ('UI 专用') then the resource, the value semantics in parentheses, and the persistence note. There is no filler and the parenthetical is well used for per-value meaning.

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 one-parameter, no-output-schema tool with no annotations, the description covers purpose, scope, all enum meanings, and persistence behavior. The only residual gap is durability semantics (where the theme is stored and whether the change applies immediately), which is minor at this complexity.

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?

Schema coverage is 0% and the enum lists bare values with no per-value descriptions. The description compensates by explaining each mode's meaning: auto follows the host, light is light parchment, dark is dark warm charcoal. That is genuine semantics added beyond the schema, though it does not address the default or reset behavior.

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+resource: it sets the appearance theme mode, and it names the three modes (auto/light/dark) with short characterizations ('浅色羊皮纸', '深色暖炭'). It does not explicitly distinguish itself from a sibling theme tool, but no sibling listed is a plausible alternative, so the purpose is unambiguous.

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 专用' (UI-only) gives a clear scope constraint about when this tool applies, and '轻量持久化' implies it is for persisting a preference rather than a one-off render. There are no explicit when-not conditions or named alternatives, so guidance is implied rather than spelled out.

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