Skip to main content
Glama

面灵AI 面试助手

interrupt_live_interview_answer

打断进行中的实时面试里 AI 正在输出的回答(已输出的部分保留)。只在 AI 正在输出时有效。需要用户已在网页或桌面客户端打开这场面试的页面并处于连接状态;操作由该页面执行,与用户点击对应按钮完全相同。(需要用户授权,范围 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": "interrupt_live_interview_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses that partial output is retained, that the effect is conditional on an active stream, that the action executes through the user's connected client page rather than server-side, and that it requires the interviews:write scope. These are precisely the behavioral facts an agent needs and none are derivable from the structured fields.

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?

The description is front-loaded with the action and its retention semantics, then layers preconditions, and only then the authorization note. The closing parenthetical ('需要用户授权,范围 interviews:write') slightly restates the permission idea already implied by the client-execution sentence, but the overall length is proportionate to a zero-parameter mutation tool.

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?

With no parameters, no output schema, and annotations carrying the basic safety profile, the only remaining burden is operational preconditions and side effects — both of which are covered (stream active, client connected, partial output kept, write scope required). An agent has everything needed to decide and invoke correctly.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. Nothing in the description contradicts or muddies the empty schema.

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 names a specific verb and object — interrupting the answer the AI is currently streaming inside a live interview — and adds the key outcome that the already-emitted portion is preserved. It is clearly distinct from siblings such as answer_live_interview_now, but it never names any alternative explicitly, which is what separates a 4 from a 5.

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?

The precondition '只在 AI 正在输出时有效' tells the agent exactly when the call is valid, and the requirement that the user have the interview page open in a connected web/desktop client gives the operational context. It stops short of naming what to call instead when the AI is not streaming or when the client is disconnected, so there are no explicit alternatives.

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