Skip to main content
Glama

面灵AI 面试助手

update_interview_preference

修改面试高级配置(跨设备同步,开始面试时作为默认值):只传要改的项,其余保持原样。当前值用 get_settings 查看;默认挂载的知识库 ID 取自 list_knowledge_bases 与 list_official_knowledge_bases。整段自定义提示词用 save_custom_prompt 保存。(需要用户授权,范围 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_interview_preference"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo面试语言(开场语言)
altLangsNo面试中可一键切换到的其他语言;空数组 = 单语言面试
webSearchNo实时面试允许联网搜索
answerStyleNo回答风格:keypoints 仅要点 / answerOnly 仅可照读的回答 / natural 要点 + 口语化回答 / structured 要点 + 结构化回答
enableReplayNo面试复盘(录制用户作答用于复盘;关闭后完全不使用麦克风)
customDataIdsNo默认挂载的知识库 ID(整体替换)
translateLangNo翻译语言,auto = 自动
dualLangAnswerNo双语回答
customAnswerStyleNo额外回答要求

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, openWorld=false, so the description needn't restate safety. It adds real context the annotations cannot convey: this is a partial update (只传要改的项,其余保持原样), settings sync across devices, values become defaults at interview start, and it requires user authorization with scope interviews:write. It does not say what the response contains or how conflicts/limits behave, keeping it below a 5.

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 block, front-loaded with the mutation contract, then the sources for valid values, then the auth scope. Every clause carries operational information; the parenthetical packaging is dense but no sentence is filler.

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?

With 9 all-optional parameters and no output schema, an agent mostly needs the partial-update rule, valid-ID sources, and auth requirements — all present. The remaining gap is what a successful response looks like and whether omitted vs explicitly empty values differ, which matters for list/array fields.

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 100% with rich enum descriptions, so the baseline would be 3. The description adds meaning beyond the schema: the partial-update contract (unpassed fields keep their current value, notably against customDataIds' 整体替换 semantics) and the provenance of valid knowledge-base IDs. It doesn't clarify edge interactions such as empty-array vs omitted values, so it isn't a 5.

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 (修改面试高级配置) plus the two distinguishing traits that separate it from siblings: cross-device sync and use as the default at interview start. It also names the sibling tools that cover adjacent operations (get_settings, list_knowledge_bases, save_custom_prompt), so an agent can route without inspecting schemas.

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

Usage Guidelines5/5

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

Explicit guidance is given for when to use this tool (change advanced interview preferences), how to read current values (get_settings), where valid knowledge-base IDs come from (list_knowledge_bases / list_official_knowledge_bases), and which alternative handles full prompt text (save_custom_prompt). These are concrete alternatives with the conditions that select them.

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