Skip to main content
Glama

面灵AI 面试助手

set_live_interview_options

修改进行中的实时面试的设置:识别语言(只能在开场时选定的语言集合内切换,切换后页面自动重连一次)、自动回答(关闭后只在「立即回答」时作答)、一题一卡(同一道题的续说与追问归入一张卡)。自动回答与一题一卡只有桌面客户端的面试浮窗支持。只传要改的项。需要用户已在网页或桌面客户端打开这场面试的页面并处于连接状态;操作由该页面执行,与用户点击对应按钮完全相同。(需要用户授权,范围 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": "set_live_interview_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo识别语言
turnCardsNo一题一卡
autoAnswerNo自动回答

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the side effect that the page reconnects once after a language switch, that the call triggers the exact same code path as a user clicking the button, that the operation is executed by the open client page rather than server-side, and that it needs the interviews:write scope. The non-destructive mutation profile is consistent with the annotations but the description supplies the operational consequences the annotations cannot.

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-loaded with the resource being modified and information-dense throughout, with no filler sentences. The nested parentheticals and single long run-on paragraph make it slightly harder to scan than it could be, but every clause carries actionable constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-optional-parameter mutation with no output schema and only minimal annotations, everything an agent needs is present: prerequisites, per-field behavior, platform limitations, permission scope, and partial-update semantics. Nothing material is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions are one-word labels, so the description carries the real semantics: lang is constrained to the opening-time language set and causes a reconnect, autoAnswer=false means it answers only on explicit '立即回答', and turnCards groups continuations and follow-ups of one question into a single card. The partial-update rule ('只传要改的项') resolves the ambiguity of three optional booleans.

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: it modifies settings of an already-running live interview, and it enumerates the three settings affected (recognized language, auto-answer, one-card-per-question). The 'live/进行中' framing implicitly separates it from mock-interview siblings such as set_mock_interview_assist, so an agent can select it without opening any 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?

Gives explicit when/when-not conditions: the language can only be switched within the set chosen at the opening, auto-answer and one-card mode are desktop-client-only, and only fields to be changed should be passed. It also names a hard prerequisite (user must have the session page open and connected) that determines whether the call can succeed at all.

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