Skip to main content
Glama

面灵AI 面试助手

update_client_settings

修改桌面客户端的云端设置(快捷键、浮窗样式、档位、自动回答、静音判定时长、伪装、主题等):只传要改的项,其余保持原样;overlayStyle、actionHotkeys、disguise 按键合并。当前值用 get_settings 查看。客户端在下次启动或登录时取用云端设置;若在此之前用户在客户端本机改过任一设置,以本机为准。(需要用户授权,范围 interviews:write)

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

Input Schema

NameRequiredDescriptionDefault
themeNo外观主题:system / light / dark
localeNo界面语言;null = 跟随系统
uiScaleNo主窗口界面缩放倍率
disguiseNo自定义进程名与窗口标题,按键合并
examModeNo笔试能力档:instant 秒答 / quick 快速 / programming 编程
turnCardsNo
autoAnswerNo面试官说完后自动回答;关闭后仅在用户点击「立即回答」时作答
answerFirstNo
audioSourceNo面试方式:SPEAKER 线上面试(采集系统音频)/ PHONE 电话面试(采集麦克风)
newestFirstNo
panicHotkeyNo应急隐藏键
hotkeySchemeNo未单独修改的动作采用的默认键位方案:simple 简洁 / conflict-free 防冲突
overlayStyleNo浮窗样式,按键合并:theme、interviewBgOpacity / examBgOpacity(底色浓度 0–1)、interviewTextOpacity / examTextOpacity(文字透明度 0–1)、interviewBorderOpacity / examBorderOpacity、fontScale(字号倍率 0.3–4)、textBold、textHalo、scrollSpeed(0.05–5)、hotkeyOpacityStep、examSolveHoverMs、interviewWidth / interviewHeight / examWidth / examHeight(像素)
actionHotkeysNo浮窗动作快捷键,按键合并,值为 Tauri 键位串(如 CommandOrControl+Shift+Enter)。动作名:answer capture voice-ask scroll-up scroll-down move-left move-right move-up move-down copy-code size-up size-down opacity-up opacity-down text-opacity-up text-opacity-down auto-palette restore-palette
nativeExamOsdNo
silenceGateMsNo面试官停顿多久视为提问结束(毫秒,300–6000)
examDualCameraNo
followNewRoundNo
solverExamModeNo面试中截屏答题的能力档:instant / quick / programming
followStreamingNo
hideFromTaskbarNo
showHotkeyHintsNo
autoOpenMockShellNo
showExamReasoningNo
showCopyCodeButtonNo
interviewDualCameraNo
overlayStylePresetsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare non-read-only, non-destructive, non-open-world. The description adds real behavioral context the annotations cannot: partial-update semantics, deep key-merge for overlayStyle/actionHotkeys/disguise, that changes only take effect at next client startup or login, that a local user change wins over the cloud value, and that the call requires user authorization with scope interviews:write.

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?

One dense paragraph, but front-loaded with purpose and partial-update semantics before timing, precedence, and authorization notes. No filler sentences; the only cost is that the trailing parenthetical about auth scope reads as an afterthought.

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 27-parameter mutation tool with no output schema, the description covers the essentials: partial update, merge behavior, when changes apply, precedence conflicts, and authorization. It could have noted that unknown properties are rejected (additionalProperties: false) or what the response contains, but nothing critical is missing.

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?

With 27 parameters and only 48% schema description coverage, the description should carry more weight. It names a handful of setting groups and emphasizes key-merge for the three nested objects, but this largely restates what the schema already says and leaves roughly half the parameters (many booleans like followNewRound, newestFirst, interviewDualCamera) undocumented in either place. Baseline 3 for partially compensating.

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?

States a specific verb and resource (modify desktop client cloud settings) and then enumerates the setting families covered (hotkeys, overlay style, capability tier, auto-answer, silence threshold, disguise, theme). It explicitly contrasts itself with the read-only counterpart get_settings, so an agent can route without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage rules: pass only the fields to change, everything else stays as-is, and use get_settings to read current values first. It also explains the local-overrides-cloud precedence, which tells the agent when a write may effectively be ignored. It stops short of naming any explicit exclusions or a sibling for exam/interview-specific settings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources