Skip to main content
Glama

面灵AI 面试助手

answer_live_interview_now

Destructive

在进行中的实时面试里按「立即回答」:以面试官刚说的、还没回答的那段话(至少 6 个字)立即作答;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": "answer_live_interview_now"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation: it discloses that the action is executed by the already-open page (identical to the user clicking the button), that an in-flight AI answer will be interrupted first, and that it consumes the user's duration/quota or incurs payment. It also states the auth scope (interviews:write) and mandates explaining charges and getting consent before execution.

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?

Front-loads the core action in the first clause, then layers trigger condition, prerequisites, execution model, and billing/auth in descending order of importance. Every clause carries operational information (minimum 6 characters, interrupt-first, consent requirement); nothing is restated from the schema or annotations.

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 zero-parameter, no-output-schema action tool, the description covers everything needed to call it correctly: trigger condition, environmental prerequisite, exact semantic equivalence to a UI click, side effects on an in-flight answer, billing, and required scope. No relevant invocation detail is missing.

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 the schema has nothing to explain and the description correctly adds no parameter detail. The implicit inputs it does describe — the target being the interviewer's last unanswered utterance and an active page connection — are exactly the ambient preconditions an agent needs, though they are not schema fields.

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 in context: press "answer now" during an in-progress live interview, answering the interviewer's just-spoken, unanswered segment (min 6 characters). It is clearly distinguishable from adjacent siblings such as interrupt_live_interview_answer (this tool interrupts only as a precondition to answering) and answer_exam_now (exam vs. live interview).

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 an explicit trigger condition (use it when auto-answer is disabled) plus hard prerequisites: the user must have the interview page open in web or desktop client and be connected. It does not state when NOT to use it or name an alternative tool for the auto-answer-on case, which keeps it short of a 5.

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