Skip to main content
Glama

面灵AI 面试助手

update_exam_customization

修改笔试 / 面试截图答题的定制偏好(跨设备同步,桌面客户端下次启动时取用):只传要改的项,其余保持原样。当前值用 get_settings 查看;整段自定义答题提示词用 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_exam_customization"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeModeNo代码模式:auto 跟随题目 / acm 完整程序含输入输出 / core 只写核心函数
codeQualityNo代码风格:standard 标准 / readable 易读 / concise 简洁 / performance 性能优先
quickPromptsNo常驻快捷指令(答题浮窗中一键发送的追问,整体替换,最多 8 条)
answerLanguageNo讲解所用语言;auto = 笔试跟随界面语言、面试中跟随面试语言
customRequirementsNo补充要求
programmingLanguageNo编程题所用语言,如 Python、Java、C++;auto = 跟随题目

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Adds real context beyond the annotations: cross-device sync, desktop client consumption on next launch, and a required user authorization scope (interviews:write). It does not cover validation failures, whether changes are reversible, or what a sync conflict looks like, so it stops short of a full behavioral picture for a write tool.

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?

Front-loads the action and resource, then packs scope, partial-update rule, sibling routing and auth into a compact sentence with no filler. The dense stacked parentheticals make it slightly heavy to scan, but every clause carries information.

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?

Covers purpose, alternatives, auth scope and edit semantics for a 6-parameter all-optional mutation tool. Missing is only edge-case behavior such as what happens on cross-device sync conflict or invalid enum values, which is minor given full schema coverage.

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 coverage is 100% with self-documenting enums, so the schema already carries the field-level meaning and the baseline is 3. The description adds only the cross-cutting partial-update rule, not per-field nuance such as how customRequirements relates to the prompt saved by save_custom_prompt.

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 (修改) plus a precise resource (笔试/面试截图答题的定制偏好), and immediately distinguishes itself from get_settings (viewing) and save_custom_prompt (full prompt). An agent can tell what this does and what it does not do 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 Guidelines5/5

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

Explicitly routes the agent: read current values via get_settings, save a whole custom prompt via save_custom_prompt, and use this tool only for incremental edits. The partial-update rule ('只传要改的项,其余保持原样') is stated as an operating instruction rather than left to inference.

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